Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-1
Severity: grave
Justification: renders docker unusable
Control: affects -1 docker.io
After upgrading to 1.0.0~rc2+git20161109.131.5137186-1 , docker
containers fail to start:
Cannot start service web: rpc error: code = 2 desc = "oci runt
Felipe Sateler wrote:
> Cannot start service web: rpc error: code = 2 desc
> = "oci runtime error: flag provided but not defined: -bundle"
I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.or
Hi,
> runc: 1.0 release candidate breaks docker 1.11 - oci
> runtime error: flag provided but not defined: -bundle
… and anyone seeing "bad listen address format
/var/run/docker/libcontainerd/docker-containerd.sock, expected proto://address"
will temporarily need to downgrade containerd too. :)
Package: runc
Version: 1.0.0~rc2+git20161109.131.5137186-2
Followup-For: Bug #855208
Do, now with Breaks,
doing
apt-get dist-upgrade --purge
installs new runc, at the expense of removing docker.io from the sytem.
It would be better to not upgrade any of these.
How about removing or holding off
On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
> Felipe Sateler wrote:
>
>> Cannot start service web: rpc error: code = 2 desc
>> = "oci runtime error: flag provided but not defined: -bundle"
>
> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
Hi everyone. This upload i
Potter, Tim wrote:
> On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
> Hi everyone. This upload is part of updated build dependencies for Docker
> 1.13.0.
> Currently the pipeline is stalled while a few things sit in the NEW queue.
> When
> that's all sorted out everything should build again.
On 16 Feb 2017, at 9:56 AM, Chris Lamb wrote:
>
> Potter, Tim wrote:
>
>> On 16 Feb 2017, at 9:06 AM, Chris Lamb wrote:
>
>> Hi everyone. This upload is part of updated build dependencies for Docker
>> 1.13.0.
>> Currently the pipeline is stalled while a few things sit in the NEW queue.
>>
Hi Tim,
On Wed, Feb 15, 2017 at 10:52:22PM +, Potter, Tim wrote:
> > I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
>
> Hi everyone. This upload is part of updated build dependencies for Docker
> 1.13.0.
> Currently the pipeline is stalled while a few things sit in th
On 18 Feb 2017, at 5:33 AM, Evgeni Golov wrote:
>
> Hi Tim,
>
> On Wed, Feb 15, 2017 at 10:52:22PM +, Potter, Tim wrote:
>>> I can reproduce this. Downgrading to 0.1.1+dfsg1-2 fixed this for me.
>>
>> Hi everyone. This upload is part of updated build dependencies for Docker
>> 1.13.0.
>>
Hi Tim,
On Mon, Feb 20, 2017 at 11:38:29PM +, Potter, Tim wrote:
> On 18 Feb 2017, at 5:33 AM, Evgeni Golov wrote:
> > Can we in the meantime have proper Breaks in place, so that people don't
> > accidentally update runc without docker/containerd/etc?
>
> Hi Evgeni. Thanks for the reply.
10 matches
Mail list logo
