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
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
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
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.
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
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.
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
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
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.
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
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
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.
12 matches
Mail list logo
