On 4/12/20 7:49 PM, Chris Lamb wrote:
severity 956502 serious
thanks
Hi,
docker: Error response from daemon: no status provided on response: unknown.
This, too, happens for me. Downgrading to 19.03.6+dfsg1-2 (from
19.03.6+dfsg1-3) restores all functionality.
Marking as RC merely to prevent migration to bullseye (which still has
19.03.6+dfsg1-2).
Thanks!
So far I had some success by replacing the binary
/usr/bin/docker-containerd by the one mentioned by upstream, either one of:
-
https://download.docker.com/linux/debian/dists/buster/pool/stable/amd64/containerd.io_1.2.10-3_amd64.deb
-
https://download.docker.com/linux/debian/dists/buster/pool/stable/amd64/containerd.io_1.2.10-2_amd64.deb
While the older version available on their mirror shows the same issue
that we're hitting:
-
https://download.docker.com/linux/debian/dists/buster/pool/stable/amd64/containerd.io_1.2.6-3_amd64.deb
It's unfortunate that upstream does not provide a source package for
containerd.io, they only provide the binary package AFAIK.
~~ For more understanding on this bug ~~
Note that Docker upstream uses two different versions of containerd:
- one version of containerd is used to build docker (ie. it's part of
the dependency tree in the vendor/ directory). At the moment they use a
commit that is on the master branch, somewhere between `v1.2.0` and
`v1.3.0-beta.0`.
- another version of containerd is used to build the containerd binary,
then is packaged as `containerd.io`, and is installed as a dependency of
`docker.io`. This package is built from a tagged version, on the
`release/1.2` branch. So it's kind of "stable".
While for Debian packaging, we use only the version that is mentioned in
the vendor tree (so the commit from the master branch), for both
purpose: building the docker package and also building the
docker-containerd binary that is then installed along with docker.
So here I would say that we need to find a patch in containerd, that
should be on the 1.2 branch. That's my best guess.
