alibaba / cloud-kernel Goto Github PK

Cloud Kernel - an open-source Linux kernel originated by Alibaba Operating System Team

Home Page: https://alibaba.github.io/cloud-kernel

License: Other

Makefile 0.26% Roff 0.02% C 97.93% Assembly 1.36% C++ 0.03% Shell 0.13% Perl 0.13% Awk 0.01% Python 0.10% sed 0.01% Yacc 0.02% Lex 0.01% UnrealScript 0.01% Gherkin 0.01% XS 0.01% Clojure 0.01% M4 0.01% SmPL 0.02% Raku 0.01%

linux kernel aliyun aliyunlinux os alibabacloud ecs alibabacloudlinux

cloud-kernel's Introduction

# 【公告】github Cloud-Kernel仓库已停用
--------------------------------------

Cloud-Kernel 已迁移至 OpenAnolis 龙蜥社区，本仓库已停用，不再进行后续更新和维护。  
具体请移步龙蜥社区 Cloud Kernel SIG：https://openanolis.cn/sig/Cloud-Kernel.

Cloud Kernel has been migrated to the OpenAnolis community. This repository has been deprecated and will no longer be updated and maintained.  
For details, please visit the Cloud Kernel SIG of OpenAnolis community: https://openanolis.cn/sig/Cloud-Kernel.

cloud-kernel's People

Contributors

Stargazers

Watchers

Forkers

casparant ethercflow zhangyongsu wisen nqiu sdgdsffdsfff linux-kern 0x0916 beaver-company zhenshuitieniu servicefoundation lukehuang ufo001sos002 albertygu assassinlx misselvexu mjymozart gridl wrathli skymysky d1jk wd21303 jackrambor wanghaibo st-rnd qiongqiong520 haoshao windofthesky simplecoka centuser grisson rousya zyb521 cuimingyang rockframeworks zhengqin theworldwego jekenpwn rallymanw hustpeior haosdent cybertan dongzhiyan-stack tangbinzy lyx634449800 learningendless 742362144 miraclemore zeltnerd crazyss robinzh deepanshu1422 arnavbalyan guoqingjiang-linux chengyli xianghaohyman mu-l wareric wangpeng003 wangyx0055 circle-circle gogoxiaoxiao bh1scw mirrorll jackwiy zhaodan2000 samzhangss immortal-jelly hustliyilin xueche hdp7891000 king019 arthur819 liguang-li joyceusa2011 ajunlonglive lubinszarm smith-daicb feiyunwill nwpufish chhaj5236 fengzunbao hohner2008 wenhuizhang hudawei guanxcode codemaster7000 cnst-ak47 zimengsheng abel-von wardenjohn chenk008 thanmayiakkala yongw-pur yoiy33

cloud-kernel's Issues

`CONFIG_CROSS_MEMORY_ATTACH` is not set in the kubernetes engine

Hi. I'm a developer for chaos-mesh, and we're testing chaos-mesh on the aliyun Container Kubernetes Service. However, some chaos may fail to work because CONFIG_CROSS_MEMORY_ATTACH is not set (I have checked the config through mounting the boot volume and read config-4.19.91-21.al7.x86_64. ).

root@ubuntu:/boot# cat config-4.19.91-21.al7.x86_64 |grep CONFIG_CROSS_MEMORY
# CONFIG_CROSS_MEMORY_ATTACH is not set
root@ubuntu:/boot#

It seems that the compiling config is set y for alios7 (in this config). Why it's not y for the Kubernetes engine? Is there any security or other concern?

[SoC2020] PostgreSQL: add io_uring support

项目名称/Project Title

PostgreSQL: 增加 io_uring 支持
PostgreSQL: add io_uring support

项目描述/Project Description

PostgreSQL 是一款强大的开源对象-关系数据库服务器（ORDBMS），特点是可靠，特性健壮以及高性能，且支持跨平台。PostgreSQL 的 Slogan 是“世界上最先进的开源关系型数据库”，其官网链接：https://www.postgresql.org/

本项目计划在 PostgreSQL 中增加对 io_uring 的支持，以优化异步 io 模型的性能，目前社区也有在做这方面的尝试。参考资料：https://anarazel.de/talks/2020-01-31-fosdem-aio/aio.pdf

PostgreSQL is a powerful, open source object-relational database system with over 30 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance. It supports running corss-platform. The slogan of PostgreSQL is "The World's Most Advanced Open Source Relational Database", as seen on the offical website is https://www.postgresql.org/.

This project wants to add io_uring support for PostgreSQL, to achieve better performance by using asynchronous io. Now community already has similar attempt, for more details please refer https://anarazel.de/talks/2020-01-31-fosdem-aio/aio.pdf

预期成果/Expected Outcomes

通过 PostgreSQL 自带回归测试用例
通过 pgTAP 测试套
支持 io_uring 的 PostgreSQL 版本在 Aliyun Linux 2 上能正常运行
预期相比原始版本性能有 10%+ 的提升

Pass PostgreSQL related testcases
Pass pgTAP testcases
Make PostgreSQL with io_uring support run normally on Aliyun Linux 2
Expect 10+ performance optimization compared to original version

需要的技能/Required Skills

熟悉 C 语言编程
熟悉 PostgreSQL 的基本原理机制
熟悉异步 IO（aio/io_uring）

Familiar with C
Familliar with PostgreSQL
Familliar with aio/io_uring

5.10内核在cgroup v1 是否完整支持writeback功能？

按照https://github.com/alibaba/cloud-kernel/wiki/cgroup-writeback-v1-interface文档测试5.10内核发现writeback功能并没有起到预期的效果，是哪里打开方式有问题么？

The return value of 'sscanf()' should be checked

cloud-kernel/tools/power/x86/intel-speed-select/isst-config.c

Line 1344 in c154e18

sscanf(optarg, "0x%llx", &fact_trl);

I want information

I want to add the Wi-Fi, Bluetooth connection function and the web browser application to my own operating system. but I can't find the Wi-Fi, Bluetooth connection function information on the "wiki.osdev" site, so I'd like to know where you got the related data.

[SoC2020] Support upgrading the existing D-Bus daemon without reboot

项目名称/Project Title

D-Bus: 支持热升级
Support upgrading the existing D-Bus daemon without reboot

项目描述/Project Description

D-Bus 是一个用于进程间通信的轻量级的消息总线系统，其官网链接：https://www.freedesktop.org/wiki/Software/dbus/
D-Bus 除了应用于桌面环境，现在也应用于服务器环境中。服务器作为信息时代的基石，需要 7*24 小时不间断运行，D-Bus 作为 systemd 的一个服务，也需要能够长期稳定运行。但是目前 D-Bus 不支持热升级，即升级 D-Bus 软件包之后，需要重启服务器。社区在这方面也有一些讨论：
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805449
本项目计划添加对 D-Bus 热升级的支持。

D-Bus is a lightweight message bus system for inter-process communication, and its official website link: https://www.freedesktop.org/wiki/Software/dbus/
D-Bus is used not only in the desktop environment, but also in the server environment. As the cornerstone of the information age, the server needs 7 * 24 hours of uninterrupted operation. As a service of systemd, D-Bus also needs to be able to run stably for a long time.
However, after upgrading the D-Bus software package, we need to restart the server.
The community also has some discussions:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805449
This project plans to support upgrading the existing D-Bus daemon without reboot.

预期成果/Expected Outcomes

D-Bus支持热升级之后，修复 D-Bus 的 CVE 漏洞或者 BUG 后，不用重启系统，有助于 Alibaba Cloud Linux 2 成为运行时间最长、最稳定的系统。

After supporting the upgrade of the existing dbus daemon without reboot, we can fix some D-Bus cve vulnerabilities or bugs online, which will help Alibaba Cloud Linux 2 become the longest running and most stable system.

需要的技能/Required Skills

熟悉 C/C++ 语言编程
D-Bus 的背景知识

Familiar with C
D-Bus related background knowledge

Alibaba Cloud Linux release 3无wireguard模块么？

Alibaba Cloud Linux release 3都升级至5.10了，是没内置wireguard模块么？

Please add "set the type of aliyun.qcow2 as virtio"

When I boot the qcow2, the default type is IDE, but it should be virtio, so could you please add that to main page?

Document /proc/sys/net/ipv4/tcp_tw_timeout interface

We implemented /proc/sys/net/ipv4/tcp_tw_timeout interface in Cloud Kernel. The usage should be documented as wiki or kb.

+tcp_tw_timeout - INTEGER
+       The length of time (in seconds) a connection will remain in the
+       TIME-WAIT state. The maximum value is 600 seconds, the minimum
+       value is 1 second.
+       It should not be changed without advice/request of technical
+       experts.
+       Default: 60 seconds

Missing a Dingtalk Group for Ali linux .

Hi , i am happy to see alibaba anolis os open.
Missing a Dingtalk group for community.

AliyunLinux2 创建快照/镜像后产生无用的 aliyun-base.repo 引起报错

[问题描述]：

用公共镜像，yum update 了一下系统
制作快照
停机后回滚快照，生成了 aliyun-base 的repo。（初步怀疑是cloud-init出来的，因为初始的公共镜像只有 AliYun 的 repo）
里面的baseurl是 http://mirrors.cloud.aliyuncs.com/aliyunlinux/15.01/os/$basearch/，这个地址下只有 15.01 的老的库，没有2版本的库，引用系统变量，yum 就会报错。

有修改 os-release 和 alinux-release 为 CentOS，可能会成为干扰项导致cloud-init出错

[建议方案]：

修复 cloud-init 相关问题

已经同步至聆听平台： https://connect.aliyun.com/suggestion/142611

怎么为特定版本内核生成btf文件？

如题

snap doesn't meet dependency requirements

I was trying to install snapd on Alibaba Cloud Linux 2. And it seems that selinux-policy-base is too old in repo.
I have yum update everything to the latest version.

[root@cn-hongkong-aliyun-cn-hongkong-1582695960 ~]# yum install snapd
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
Resolving Dependencies
--> Running transaction check
---> Package snapd.x86_64 0:2.47.1-1.el7 will be installed
--> Processing Dependency: snap-confine(x86-64) = 2.47.1-1.el7 for package: snapd-2.47.1-1.el7.x86_64
--> Processing Dependency: snapd-selinux = 2.47.1-1.el7 for package: snapd-2.47.1-1.el7.x86_64
--> Processing Dependency: squashfs-tools for package: snapd-2.47.1-1.el7.x86_64
--> Processing Dependency: squashfuse for package: snapd-2.47.1-1.el7.x86_64
--> Running transaction check
---> Package snap-confine.x86_64 0:2.47.1-1.el7 will be installed
---> Package snapd-selinux.noarch 0:2.47.1-1.el7 will be installed
--> Processing Dependency: selinux-policy-base >= 3.13.1-268.el7 for package: snapd-selinux-2.47.1-1.el7.noarch
--> Processing Dependency: policycoreutils-python for package: snapd-selinux-2.47.1-1.el7.noarch
---> Package squashfs-tools.x86_64 0:4.3-0.21.gitaae0aff4.1.al7 will be installed
---> Package squashfuse.x86_64 0:0.1.102-1.el7 will be installed
--> Processing Dependency: squashfuse-libs(x86-64) = 0.1.102-1.el7 for package: squashfuse-0.1.102-1.el7.x86_64
--> Processing Dependency: libfuseprivate.so.0()(64bit) for package: squashfuse-0.1.102-1.el7.x86_64
--> Processing Dependency: libsquashfuse.so.0()(64bit) for package: squashfuse-0.1.102-1.el7.x86_64
--> Processing Dependency: libzstd.so.1()(64bit) for package: squashfuse-0.1.102-1.el7.x86_64
--> Running transaction check
---> Package libzstd.x86_64 0:1.4.5-3.el7 will be installed
---> Package policycoreutils-python.x86_64 0:2.5-34.1.al7 will be installed
--> Processing Dependency: setools-libs >= 3.3.8-4 for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libsemanage-python >= 2.5-14 for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: audit-libs-python >= 2.1.3-4 for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: python-IPy for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libqpol.so.1(VERS_1.4)(64bit) for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libqpol.so.1(VERS_1.2)(64bit) for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libcgroup for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libapol.so.4(VERS_4.0)(64bit) for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: checkpolicy for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libqpol.so.1()(64bit) for package: policycoreutils-python-2.5-34.1.al7.x86_64
--> Processing Dependency: libapol.so.4()(64bit) for package: policycoreutils-python-2.5-34.1.al7.x86_64
---> Package snapd-selinux.noarch 0:2.47.1-1.el7 will be installed
--> Processing Dependency: selinux-policy-base >= 3.13.1-268.el7 for package: snapd-selinux-2.47.1-1.el7.noarch
---> Package squashfuse-libs.x86_64 0:0.1.102-1.el7 will be installed
--> Running transaction check
---> Package audit-libs-python.x86_64 0:2.8.5-4.1.al7 will be installed
---> Package checkpolicy.x86_64 0:2.5-8.1.al7 will be installed
---> Package libcgroup.x86_64 0:0.41-21.1.al7 will be installed
---> Package libsemanage-python.x86_64 0:2.5-14.1.al7 will be installed
---> Package python-IPy.noarch 0:0.75-6.1.al7 will be installed
---> Package setools-libs.x86_64 0:3.3.8-4.1.al7 will be installed
---> Package snapd-selinux.noarch 0:2.47.1-1.el7 will be installed
--> Processing Dependency: selinux-policy-base >= 3.13.1-268.el7 for package: snapd-selinux-2.47.1-1.el7.noarch
--> Finished Dependency Resolution
Error: Package: snapd-selinux-2.47.1-1.el7.noarch (epel)
           Requires: selinux-policy-base >= 3.13.1-268.el7
           Installed: selinux-policy-targeted-3.13.1-266.1.al7.1.noarch (@anaconda)
               selinux-policy-base = 3.13.1-266.1.al7.1
           Available: selinux-policy-minimum-3.13.1-229.1.al7.noarch (base)
               selinux-policy-base = 3.13.1-229.1.al7
           Available: selinux-policy-minimum-3.13.1-229.6.al7.noarch (updates)
               selinux-policy-base = 3.13.1-229.6.al7
           Available: selinux-policy-minimum-3.13.1-229.7.al7.9.noarch (updates)
               selinux-policy-base = 3.13.1-229.7.al7.9
           Available: selinux-policy-minimum-3.13.1-229.8.al7.12.noarch (updates)
               selinux-policy-base = 3.13.1-229.8.al7.12
           Available: selinux-policy-minimum-3.13.1-229.9.al7.15.noarch (updates)
               selinux-policy-base = 3.13.1-229.9.al7.15
           Available: selinux-policy-minimum-3.13.1-252.1.al7.1.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.1
           Available: selinux-policy-minimum-3.13.1-252.1.al7.6.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.6
           Available: selinux-policy-minimum-3.13.1-266.1.al7.noarch (updates)
               selinux-policy-base = 3.13.1-266.1.al7
           Available: selinux-policy-minimum-3.13.1-266.1.al7.1.noarch (updates)
               selinux-policy-base = 3.13.1-266.1.al7.1
           Available: selinux-policy-mls-3.13.1-229.1.al7.noarch (base)
               selinux-policy-base = 3.13.1-229.1.al7
           Available: selinux-policy-mls-3.13.1-229.6.al7.noarch (updates)
               selinux-policy-base = 3.13.1-229.6.al7
           Available: selinux-policy-mls-3.13.1-229.7.al7.9.noarch (updates)
               selinux-policy-base = 3.13.1-229.7.al7.9
           Available: selinux-policy-mls-3.13.1-229.8.al7.12.noarch (updates)
               selinux-policy-base = 3.13.1-229.8.al7.12
           Available: selinux-policy-mls-3.13.1-229.9.al7.15.noarch (updates)
               selinux-policy-base = 3.13.1-229.9.al7.15
           Available: selinux-policy-mls-3.13.1-252.1.al7.1.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.1
           Available: selinux-policy-mls-3.13.1-252.1.al7.6.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.6
           Available: selinux-policy-mls-3.13.1-266.1.al7.noarch (updates)
               selinux-policy-base = 3.13.1-266.1.al7
           Available: selinux-policy-mls-3.13.1-266.1.al7.1.noarch (updates)
               selinux-policy-base = 3.13.1-266.1.al7.1
           Available: selinux-policy-targeted-3.13.1-229.1.al7.noarch (base)
               selinux-policy-base = 3.13.1-229.1.al7
           Available: selinux-policy-targeted-3.13.1-229.6.al7.noarch (updates)
               selinux-policy-base = 3.13.1-229.6.al7
           Available: selinux-policy-targeted-3.13.1-229.7.al7.9.noarch (updates)
               selinux-policy-base = 3.13.1-229.7.al7.9
           Available: selinux-policy-targeted-3.13.1-229.8.al7.12.noarch (updates)
               selinux-policy-base = 3.13.1-229.8.al7.12
           Available: selinux-policy-targeted-3.13.1-229.9.al7.15.noarch (updates)
               selinux-policy-base = 3.13.1-229.9.al7.15
           Available: selinux-policy-targeted-3.13.1-252.1.al7.1.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.1
           Available: selinux-policy-targeted-3.13.1-252.1.al7.6.noarch (updates)
               selinux-policy-base = 3.13.1-252.1.al7.6
           Available: selinux-policy-targeted-3.13.1-266.1.al7.noarch (updates)
               selinux-policy-base = 3.13.1-266.1.al7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

The OS info

[root@cn-hongkong-aliyun-cn-hongkong-1582695960 ~]# uname -a
Linux cn-hongkong-aliyun-cn-hongkong-1582695960.######.com 4.19.91-21.2.al7.x86_64 #1 SMP Fri Sep 18 11:39:58 CST 2020 x86_64 x86_64 x86_64 GNU/Linux
[root@cn-hongkong-aliyun-cn-hongkong-1582695960 ~]# lsb_release -a
LSB Version:	:core-4.1-amd64:core-4.1-noarch
Distributor ID:	AlibabaCloud(AliyunLinux)
Description:	Alibaba Cloud Linux (Aliyun Linux) release 2.1903 LTS (Hunting Beagle) 
Release:	2.1903
Codename:	HuntingBeagle

Any idea on this or I have do install selinux-policy-base manually?

Thanks!

A question about systemd-nspawn

I'm having some problems with systemd-nspawn and I'm not sure if I should report it here. If it shouldn't appear here, please close it

System Information

lsb_release -a

LSB Version:    :core-4.1-amd64:core-4.1-noarch

Distributor ID: AlibabaCloud

Description:    Alibaba Cloud Linux release 3 (Soaring Falcon) 

Release:        3

Codename:       SoaringFalcon

Problem Description

Download an archlinux image file
Extract the image file with the tar command
Start the image file with systemd-nspawn
Executing pacman-key --init in this container results in an error

like this

➜  img curl -f --remote-name-all https://archive.archlinux.org/iso/2022.06.01/archlinux-bootstrap-2022.06.01-x86_64.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  159M  100  159M    0     0  10.4M      0  0:00:15  0:00:15 --:--:-- 10.7M

➜  img tar -zxvf archlinux-bootstrap-2022.06.01-x86_64.tar.gz 
 
   ---------Some decompression operations----

➜  img ls 

archlinux-bootstrap-2022.06.01-x86_64.tar.gz  root.x86_64

➜  img systemd-nspawn -D root.x86_64 

Spawning container root.x86_64 on /home/eive/img/root.x86_64.

Press ^] three times within 1s to kill container.

-bash-5.1# pacman-key --init

==> ERROR: pacman configuration file '/etc/pacman.conf' not found.

-bash-5.1# ls /etc | grep "pacman*"

pacman.conf

pacman.d

However, this file exists

Some attempts

use chroot

➜  img chroot root.x86_64  bash

[root@iZ2ze9mjsaskd7fy9i8ioeZ /]# pacman-key --init

gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/AF76249FE74363ACD220398458CBB6E9C488DE86.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u

It works fine

####use debian

eive@eive-allseries:~/temp$ curl -f --remote-name-all https://archive.archlinux.org/iso/2022.06.01/archlinux-bootstrap-2022.06.01-x86_64.tar.gz

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  159M  100  159M    0     0  3369k      0  0:00:48  0:00:48 --:--:-- 4507k

eive@eive-allseries:~/temp$ tar -zxvf archlinux-bootstrap-2022.06.01-x86_64.tar.gz 

 ---------Some decompression operations----

eive@eive-allseries:~/temp$ ls

archlinux-bootstrap-2022.06.01-x86_64.tar.gz  root.x86_64

eive@eive-allseries:~/temp$ systemd-nspawn -D root.x86_64/

Need to be root.

eive@eive-allseries:~/temp$ sudo systemd-nspawn -D root.x86_64/

Spawning container root.x8664 on /home/eive/temp/root.x86_64.

Press ^] three times within 1s to kill container.

[root@root ~]# pacman-key --init

gpg: Warning: using insecure memory!
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: Warning: using insecure memory!

---- other information ------

Also works fine

Additional Information

I tried other versions of archlinux image files and the same thing happens

failed to restrict blkio bps device with backport

I use Alinyun Linux 4.19.57 > 4.19.36 with cgwb_v1 enabled， async IO bps limits does not work. In this case, only direct io works as expected.

cloud-kernel is cgroup V2 already supported？

If inscribe

重新下载安装yum rpm包，从哪里下载，下载什么版本的？

Alibaba Cloud Linux release 3 (Soaring Falcon)

2020 Alibaba Summer of Code

Welcome to the open source world! If you haven't planned how to spend this summer, come to the Alibaba Summer of Code and coding with us! 💻

Alibaba Summer of Code is a global program focused on engaging students directly into open source software development. Under the guidance of the mentor in the Alibaba open source project, students experience the software development in the real world. Alibaba Summer of code will begin between May 25th and September 5th. Students can use the summer time to participate in the open source project and work with the core members of the project.

What you can get?

On this exclusive developer journey, students will have the opportunity to:

• Participate in the top projects of the International Open Source Foundation;
• Get a scholarship from Alibaba;
• Obtain an open source contributor certificate;
• Get a fast pass of Alibaba Internship/recruitment;
• Get your code adopted and used by the open source project！

Our Mentors

GitHub ID：josephhz
Alibaba Cloud Software Engineer, Linux Kernel Developer and OCFS2 maintainer

GitHub ID：w-simon
Alibaba Cloud Software Engineer, Linux Kernel Developer

GitHub ID：wangxiaoguang
Alibaba Cloud Software Engineer, Linux Kernel Developer

Apply Now!

Step 1. You can click on this link to apply directly:

PostgreSQL: add io_uring support #9
Support upgrading the existing D-Bus daemon without reboot #10

Step 2. Full list of Alibaba Summer of Code Projects
• 中文: https://developer.aliyun.com/topic/summerofcode2020
• English: https://www.alibabacloud.com/campaign/summerofcode2020

Timeline⏳

Contact us!

Email Address: [email protected]

tcp 传输小包返回结果有40ms延迟，跟内核tcp设计有关？

能否将intel i225的igc驱动移植到4.19的内核中

能否将intel i225的igc驱动移植到4.19的内核中?

Missing yum-plugin-releasever-adapter in Alinux 3 alinux3-plus repo

Hi,

I updated my instance to Alinux 3 and found that the package yum-plugin-releasever-adapter is missing in AliYun.repo when installing docker-ce using Docker official repo. I have searched all repos in AliYun.repo including alinux3-plus which should be named as plus in Aliunx 2.

I am wondering if there is a new way to alter $releasever in Docker repo in Aliunx 3 or the package is missing somehow.

I manually changed the repo for now but I am looking forward to having a more decent way :)

Thank you

安装docker成功,启动容器失败

使用yum -y install docker 命令安装docker后,使用docker run 命令启动镜像,镜像的状态一直是restarting,测试了好多的镜像,都是restarting,但是将操作系统换成CentOS-7.6就好了
启动镜像是docker服务的日志如下

Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.518545793+08:00" level=warning msg="Your kernel does not support cgroup rt period"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.518559425+08:00" level=warning msg="Your kernel does not support cgroup rt runtime"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.518886791+08:00" level=info msg="Loading containers: start."
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.564268110+08:00" level=info msg="Firewalld running: false"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.617425407+08:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.650312231+08:00" level=info msg="Loading containers: done."
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.672847169+08:00" level=warning msg="Not using native diff for overlay2, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.679713246+08:00" level=info msg="Daemon has completed initialization"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.679743201+08:00" level=info msg="Docker daemon" commit="7f2769b/1.13.1" graphdriver=overlay2 version=1.13.1
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:09:52.687493602+08:00" level=info msg="API listen on /var/run/docker.sock"
Sep 13 13:09:52 iZuf6j6id5y6dup93gcestZ systemd[1]: Started Docker Application Container Engine.
Sep 13 13:10:15 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:10:15.402430270+08:00" level=error msg="Handler for POST /v1.26/containers/create returned error: No such image: litongjava/ibotcluster:1.7"
Sep 13 13:11:13 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:11:13.019101870+08:00" level=error msg="Handler for POST /v1.26/containers/create returned error: No such image: litongjava/aiengine:20171020"
Sep 13 13:12:12 iZuf6j6id5y6dup93gcestZ oci-umount[1860]: umounthook <debug>: prestart container_id:6e504e96d4f8 rootfs:/var/lib/docker/overlay2/de6728905b08e1eb84ad901a66c0fdc61723e0ed037e488a2c64b8e7cb2f970b/merged
Sep 13 13:12:13 iZuf6j6id5y6dup93gcestZ dockerd-current[1562]: time="2019-09-13T13:12:13.006790546+08:00" level=warning msg="6e504e96d4f8c46b34d4dbcd7ee915110504ae3a04166a2ffbb3bc65e0aae25b cleanup: failed to unmount secrets: invalid argument"
Sep 13 13:12:13 iZuf6j6id5y6dup93gcestZ oci-umount[1969]: umounthook <debug>: prestart container_id:6e504e96d4f8

docker-ce doesn't meet dependency requirements

I met the following dependency issues when upgrading docker today.

--> Running transaction check
---> Package docker-ce-rootless-extras.x86_64 0:20.10.0-3.el7 will be installed
--> Processing Dependency: fuse-overlayfs >= 0.7 for package: docker-ce-rootless-extras-20.10.0-3.el7.x86_64
--> Processing Dependency: slirp4netns >= 0.4 for package: docker-ce-rootless-extras-20.10.0-3.el7.x86_64
--> Finished Dependency Resolution
Error: Package: docker-ce-rootless-extras-20.10.0-3.el7.x86_64 (docker-ce-stable)
           Requires: slirp4netns >= 0.4
           Available: slirp4netns-0.3.0-1.1.al7.x86_64 (extras)
               slirp4netns = 0.3.0-1.1.al7
Error: Package: docker-ce-rootless-extras-20.10.0-3.el7.x86_64 (docker-ce-stable)
           Requires: fuse-overlayfs >= 0.7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

It seems that slirp4netns does not meet the minimum version requirement (maybe it will be updated soon) and fuse-overlayfs is not available (I have enabled the Extra Repo).

My OS info

Distributor ID:	AlibabaCloud(AliyunLinux)
Description:	Alibaba Cloud Linux (Aliyun Linux) release 2.1903 LTS (Hunting Beagle) 
Release:	2.1903
Codename:	HuntingBeagle

I appreciate for engineers' work.

alibaba / cloud-kernel Goto Github PK

cloud-kernel's Introduction

cloud-kernel's People

Contributors

Stargazers

Watchers

Forkers

cloud-kernel's Issues

项目名称/Project Title

项目描述/Project Description

预期成果/Expected Outcomes

需要的技能/Required Skills

项目名称/Project Title

项目描述/Project Description

预期成果/Expected Outcomes

需要的技能/Required Skills

System Information

Problem Description

like this

Some attempts

use chroot

Additional Information

2020 Alibaba Summer of Code

What you can get?

Our Mentors

Apply Now!

Timeline⏳

Contact us!

Recommend Projects

Recommend Topics

Recommend Org