Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Witold Baryluk]

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 the new runc version from repositories?

Cheers,
Witek

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Evgeni Golov]

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.  I had totally missed the fact that people 
> could be
> doing individual package upgrades of runc (also containerd) and this would 
> muck up
> the docker.io package.
> 
> What particular Break lines would you think appropriate for this situation?  
> My initial
> guess would have been adding Depends = in docker.io, containerd and runc to
> ensure that everything is upgraded in lockstep, but I don't see where Breaks 
> can
> be applied.

I would have suggested adding "Breaks: docker.io (<< 1.12)" to both runc
and containerd, as upgrading both (separately and together) breaks
Docker in sid atm.

Not sure how you want to add a Depends with = here, as that would mean
you need to maintain those entries on each and every upload of the
packages, which does not seem practicable (and would not fix the current
docker.io package in sid).

Regards
Evgeni

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Potter, Tim]

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.
>> Currently the pipeline is stalled while a few things sit in the NEW queue.  
>> When
>> that's all sorted out everything should build again.
> 
> 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.  I had totally missed the fact that people 
could be
doing individual package upgrades of runc (also containerd) and this would muck 
up
the docker.io package.

What particular Break lines would you think appropriate for this situation?  My 
initial
guess would have been adding Depends = in docker.io, containerd and runc to
ensure that everything is upgraded in lockstep, but I don't see where Breaks can
be applied.


Thanks,

Tim.

> 
> Thanks
> Evgeni



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Chris Lamb]

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. :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Evgeni Golov]

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 the NEW queue.  
> When
> that's all sorted out everything should build again.

Can we in the meantime have proper Breaks in place, so that people don't 
accidentally update runc without docker/containerd/etc?

Thanks
Evgeni

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Potter, Tim]

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.  
>> When
>> that's all sorted out everything should build again.
> 
> Is there something I could prioritise processing in NEW that
> would help here?

Anything with "golang" in the source package name changed by t...@debian.org
would be a great help, thanks!


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Chris Lamb]

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.

Is there something I could prioritise processing in NEW that
would help here?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#855208: [pkg-go] Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Potter, Tim]

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 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.

The cluster of docker, runc, containerd and libnetwork all are tightly coupled 
and
need to be upgrade in lockstep to avoid build failures which unfortunately is
hard to achieve in practice.

I'm hoping that once 1.13 is in unstable I can keep it up to date incrementally
instead of having to spend months going from 1.11 to 1.13.


Tim.

> 
> 
> Regards,
> 
> --
>  ,''`.
> : :'  : Chris Lamb
> `. `'`  la...@debian.org / chris-lamb.co.uk
>   `-
> 
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Chris Lamb]

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.org / chris-lamb.co.uk
   `-

Bug#855208: runc: 1.0 release candidate breaks docker 1.11 - oci runtime error: flag provided but not defined: -bundle

[Felipe Sateler]

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 runtime error: flag 
provided but not defined: -bundle"

I don't know what docker version allows usage of runc 1.0 rc.

I'm tagging the severity as grave since runc appears to be a component
of docker (there are no other rdeps), and docker fails to work with this
version.

Saludos

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages runc depends on:
ii  libapparmor1  2.11.0-2
ii  libc6 2.24-9
ii  libseccomp2   2.3.1-2.1

runc recommends no packages.

runc suggests no packages.

-- no debconf information