Open ZachEddy opened 2 years ago
Cc: @fvoznika
We need to wait for Kubernetes 1.23, which uses containerd 1.4, to reach end of life before we can start using 1.5. Otherwise we loose the ability to issue security patches to 1.23 if needed. This link has the schedule for release deprecations. 1.23 end of life is set to 2023-05.
Apart from #6414, is there any other problem you're facing using containerd 1.5 with gVisor's shim?
A friendly reminder that this issue had no activity for 120 days.
This issue is unblocked, so I'll start working on it.
Description
The
containerd/containerd
dependency is currently two minor versions behind the latest release:v1.3.9
v1.5.5
There are subtle incompatibilities between gVisor and newer versions of containerd that require temporary workarounds and fixes (see #6414 and #6232). These workarounds allow gVisor users to upgrade containerd beyond v1.3, but they should eventually be removed in favor of upgrading the containerd version used by gVisor.
Is this feature related to a specific bug?
6414
6232
Do you have a specific solution in mind?
No response