On Tue, Sep 22, 2020 at 10:30 AM El boulangero <elboulang...@gmail.com> wrote: > > Then the issue must lie in this commit: > https://salsa.debian.org/docker-team/docker/-/commit/ad52cffa31359262a8e9d44daddf896c3e063dd2 > > The docker.io package didn't build anymore, due to runc `1.0.0~rc92` which > landed in debian unstable. Shengjing Zhu came up with the patch to fix that, > but it was not a straightforward patch. The issue could be in this patch. Or > maybe there's more work required to make docker.io 19.03.x work with latest > runc (ie. more patching is needed, not less, sorry :/). > > Let me say it another way: when you install docker-ce from Docker's repo, you > also get the containerd.io package, that ships the runc binary. All of these > components are basically provided altogether by docker, and they are at > versions that were tested together. While in Debian, these separate > components (containerd, runc) are packaged independently, and these are not > the same versions as the ones shipped by Docker. So sometimes we hit this > kind of issues with the Debian package. > > And to be more correct: in Debian we actually bundle containerd within the > docker.io package, because nobody has the bandwidth to try to make docker > 19.03.x build-against / work-with containerd 1.4.x. So we build the version > of containerd that is vendored in the docker source tree, and ship it in the > docker.io package. But runc is NOT bundled in, it is provided independently > by the runc package, ie. version `1.0.0~rc92`. > > I hope that this clarifies a bit what is the issue here. >
This is indeed caused by runc 1.0.0~rc92, the following patch can fix the problem. https://github.com/moby/moby/pull/41288 This patch is missed in 19.03.13, probably will be in 19.03.14 https://github.com/moby/moby/pull/41293 -- Shengjing Zhu
