yocto 元虛擬化：啟動守護進程時出錯：未安裝設備 cgroup

Question

我已經使用 Yocto 在我的嵌入式板上創建並安裝了一個內核 4.19-rt 補丁，並使用了元虛擬化層。 在我的配置文件中，我添加了以下行

DISTRO_FEATURES_append = " virtualization"
IMAGE_INSTALL_append = " docker cgroup-lite"
DISTRO_FEATURES_append = " systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
IMAGE_ROOTFS_SIZE_ext4 = "64000000"
KERNEL_FEATURES_append = " features/cgroups/cgroups.scc "

但是，登錄到我的開發板並啟動 dockerd 后，出現以下錯誤：

ERRO[2021-05-23T08:09:35.292169700Z] Failed to built-in GetDriver graph btrfs /var/lib/docker 
ERRO[2021-05-23T08:09:35.301461200Z] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. 
ERRO[2021-05-23T08:09:35.319464500Z] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. 
ERRO[2021-05-23T08:09:35.319629700Z] Failed to built-in GetDriver graph devicemapper /var/lib/docker 
INFO[2021-05-23T08:09:35.339165400Z] Graph migration to content-addressability took 0.00 seconds 
WARN[2021-05-23T08:09:35.339814100Z] Your kernel does not support cgroup memory limit 
WARN[2021-05-23T08:09:35.340049500Z] Your kernel does not support cgroup rt period 
WARN[2021-05-23T08:09:35.340145300Z] Your kernel does not support cgroup rt runtime 
WARN[2021-05-23T08:09:35.340185800Z] Unable to find blkio cgroup in mounts        
WARN[2021-05-23T08:09:35.626041100Z] Unable to find cpuset cgroup in mounts WARN[2021-05-23T08:09:35.626320800Z] mountpoint for pids not found                
Error starting daemon: Devices cgroup isn't mounted

我該如何解決這個問題？

Answer 1

我最近在我的板上解決了這個問題，看起來您需要為此啟用正確的 kernel 模塊。 將 IMAGE_INSTALL_append = " docker-contrib" 添加到您的 local.conf 並在啟動后在板上運行 /usr/share/docker/check-config.sh。 它將列出成功運行 docker 所需的所有 kernel 模塊。

您可以使用 menuconfig ( https://www.yoctoproject.org/docs/2.4/kernel-dev/kernel-dev.html#configuring-the-kernel ) 配置 kernel 並添加缺少的 Z530484C18F1AFDAF 模塊。 Docker 應該在此之后運行。

希望這會有所幫助！

Answer 2

這個問題似乎至少在最新的 Kirkstone LTS 中得到了解決。 我使用你的local.conf沒有得到這樣的錯誤。