Re: [Buildroot] [PATCH v1 1/1] package/containerd: bump version to v1.6.22

[Peter Korsgaard <peter@korsgaard.com>]

>>>>> "Stefan" == Stefan Agner <stefan@agner.ch> writes:

 > Hi Christian,
 > Finally came around looking into this a bit more closely. It seems that
 > containerd just didn't send the sd notification READY=1.

 > It seems that the problem is caused by the CRI plug-in. The plug-in
 > reports the following error:
 > time="2023-09-24T21:43:20.958509027Z" level=warning msg="failed to load
 > plugin io.containerd.grpc.v1.cri" error="failed to create CRI service:
 > failed to create cni conf monitor for default: failed to create the
 > parent of the cni conf dir=/etc/cni: mkdir /etc/cni: read-only

 > We are running containerd on a read-only squashfs. I guess this explains
 > also why you haven't seen this issue.

 > After disabling the plug-in via /etc/containerd/config.toml
 > disabled_plugins = [ "cri" ], the issue disappeared (containerd service
 > starts up correctly and prints the message "containerd successfully
 > booted in ...s"

 > Checking the changelog of v1.6.22 brings up this change:
 > https://github.com/containerd/containerd/pull/8826

 > The error above was already present before, so I didn't give it much
 > attention. But I guess the change to use atomicfile really changed the
 > behavior and now seems to cause the hang on startup.

 > In any case, from my point of view, nothing which needs to be addressed
 > in Buildroot.

If cri is only needed for when containerd is used with kubernetes, then
perhaps we should disable it by default so other people don't need to
debug the same issue.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot