Samuel Karp
Samuel Karp
https://github.com/containerd/containerd/releases/tag/v1.7.22 and https://github.com/containerd/containerd/releases/tag/v1.6.36 contain the fix for this issue.
> after it has received the initial set of pods and containers but before it is has been fully registered for event processing. It seems to me that the order...
Access to the containerd socket is equivalent to root. We do not generally encourage expanding access to the socket beyond UID 0/GID 0. Unprivileged users who need access to the...
This looks to be related to the 0.1.0-style of plugins? I don't know that we need to preserve the commit.
Maybe we can clarify that we prefer GHSA without completely removing the mailing list? There can still be use-cases for the mailing list such as attachments, which don't work as...
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/containerd_containerd/9766/pull-containerd-node-e2e/1754745360544174080/artifacts/tmp-node-e2e-f8fc27d0-cos-beta-109-17800-66-81-system.log ``` Feb 06 06:17:06 tmp-node-e2e-f8fc27d0-cos-beta-109-17800-66-81 containerd[3207]: containerd: load required plugin io.containerd.grpc.v1.cri: unable to load CRI image service plugin dependency: invalid cri image config: `mirrors` is no longer supported since...
/ok-to-test
Can you fix the commit title and PR description? "Remove git depth" is not really what this commit is about.
It looks like the commit message is still "Remove git depth". Can you fix that to be descriptive for what the commit actually is? Our [contribution guide](https://github.com/containerd/project/blob/main/CONTRIBUTING.md#commit-messages) covers expectations for...