Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
Hi Dmitry, I tested the package from incoming and the error persists for me. I'm running up-to-date sid version. Let me know if you need any more information from my system. Greets. El lun., 13 de abr. de 2020 a la(s) 09:24, Dmitry Smirnov (only...@debian.org) escribió: > > On Monday, 13 April 2020 4:32:06 PM AEST Shengjing Zhu wrote: > > But compared to docker.io 19.03.6+dfsg1-2 and 19.03.6+dfsg1-3, the > > buildinfos[1] show that both used > > golang-github-containerd-ttrpc-dev/0.0~git20190828.92c8520-2. > > > > I'm afraid it's because of the changes in grpc libraries. But I have > > no clue about it, since containerd is not using grpc, but ttrpc. > > That was a crucial hint -- thanks! Somehow we were still using vendored > "ttrpc" and switching to newer system one seems to fix the problem. > > -- > Cheers, > Dmitry Smirnov. > > --- > > If liberty means anything at all, it means the right to tell people what > they do not want to hear. > -- George Orwell
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
On Monday, 13 April 2020 4:32:06 PM AEST Shengjing Zhu wrote: > But compared to docker.io 19.03.6+dfsg1-2 and 19.03.6+dfsg1-3, the > buildinfos[1] show that both used > golang-github-containerd-ttrpc-dev/0.0~git20190828.92c8520-2. > > I'm afraid it's because of the changes in grpc libraries. But I have > no clue about it, since containerd is not using grpc, but ttrpc. That was a crucial hint -- thanks! Somehow we were still using vendored "ttrpc" and switching to newer system one seems to fix the problem. -- Cheers, Dmitry Smirnov. --- If liberty means anything at all, it means the right to tell people what they do not want to hear. -- George Orwell signature.asc Description: This is a digitally signed message part.
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
On Mon, Apr 13, 2020 at 2:52 PM Shengjing Zhu wrote: > > On Mon, Apr 13, 2020 at 12:05 PM Arnaud Rebillout > wrote: > [...] > > It's unfortunate that upstream does not provide a source package for > > containerd.io, they only provide the binary package AFAIK. > > Though the packaging source is not available, their CI scripts are there. > https://github.com/moby/moby/blob/19.03/hack/dockerfile/install/containerd.installer > It seems they just build from containerd upstream tree. It seems I missed something, it's https://github.com/docker/containerd-packaging -- Shengjing Zhu
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
On Mon, Apr 13, 2020 at 12:05 PM Arnaud Rebillout wrote: [...] > It's unfortunate that upstream does not provide a source package for > containerd.io, they only provide the binary package AFAIK. Though the packaging source is not available, their CI scripts are there. https://github.com/moby/moby/blob/19.03/hack/dockerfile/install/containerd.installer It seems they just build from containerd upstream tree. -- Shengjing Zhu
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
On Mon, Apr 13, 2020 at 2:05 PM Arnaud Rebillout wrote: > > For what it's worth, I could rebuild containerd packages from the 1.2 > series, starting from [1] and iterating with different containerd versions. > > Starting from containerd version 1.2.7, the containerd binary produced > works. So it looks like we're looking for a change between 1.2.6 and 1.2.7. > > A notable change between those two versions is the update of the > dependency containerd-ttrpc. But compared to docker.io 19.03.6+dfsg1-2 and 19.03.6+dfsg1-3, the buildinfos[1] show that both used golang-github-containerd-ttrpc-dev/0.0~git20190828.92c8520-2. I'm afraid it's because of the changes in grpc libraries. But I have no clue about it, since containerd is not using grpc, but ttrpc. [1] https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=19.03.6%2Bdfsg1-2&stamp=1582680638&raw=0 https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=19.03.6%2Bdfsg1-3&stamp=1586598671&raw=0 -- Shengjing Zhu
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
For what it's worth, I could rebuild containerd packages from the 1.2 series, starting from [1] and iterating with different containerd versions. Starting from containerd version 1.2.7, the containerd binary produced works. So it looks like we're looking for a change between 1.2.6 and 1.2.7. A notable change between those two versions is the update of the dependency containerd-ttrpc. [1]: https://salsa.debian.org/go-team/packages/containerd/-/commit/c9e2aa545934b326d7f81cb267369772ab51f3f7 On 4/13/20 10:58 AM, Arnaud Rebillout wrote: 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.
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
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.
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
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). Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
On 4/12/20 3:24 PM, Arnaud Rebillout wrote: I'm trying to update the package to 19.03.7, to see if it "magically" fixes the issue. 19.03.7 does not fix anything.
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
There's an issue that was opened upstream a while ago (Oct 2019), it seems to be the same bug: https://github.com/docker/for-linux/issues/813 Unfortunately, the solution offered by upstream is to download a new version of the containerd binary. There's no reference to the actual fix. I'm trying to update the package to 19.03.7, to see if it "magically" fixes the issue. On 4/12/20 2:51 PM, Andreas Kurth wrote: Same here. In contrast to previous similar issues, even reboot and recreation of images/containers did not help. Had to downgrade, too. 5.5.0-1-amd64 #1 SMP Debian 5.5.13-2 (2020-03-30) x86_64 GNU/Linux
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
Same here. In contrast to previous similar issues, even reboot and recreation of images/containers did not help. Had to downgrade, too. 5.5.0-1-amd64 #1 SMP Debian 5.5.13-2 (2020-03-30) x86_64 GNU/Linux
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
Package: docker.io Version: 19.03.6+dfsg1-3 Severity: important Dear Maintainer, After upgrade docker.io to 19.03.6+dfsg1-3 today, container cannot start, and show the error message like below: docker: Error response from daemon: no status provided on response: unknown. Downgrade to 19.03.6+dfsg1-2 solved the issue. Thanks. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker.io depends on: ii adduser 3.118 pn iptables ii libc6 2.30-4 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libltdl72.4.6-14 ii libnspr42:4.25-1 ii libnss3 2:3.51-1 ii libseccomp2 2.4.3-1 ii libsystemd0 245.4-3 ii lsb-base11.1.0 pn runc pn tini Versions of packages docker.io recommends: ii ca-certificates 20190110 pn cgroupfs-mount pn git pn needrestart ii xz-utils 5.2.4-1+b1 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs 5.6-1 pn debootstrap pn docker-doc ii e2fsprogs1.45.6-1 pn rinse pn xfsprogs pn zfs-fuse | zfsutils
