Your message dated Fri, 18 Aug 2017 18:16:49 +0200
with message-id <9b091877-c9aa-bdda-3f7a-49e4529b0...@canonical.com>
and subject line Re: Bug#855208: [pkg-go] Bug#855208: docker still broken
has caused the Debian Bug report #855208,
regarding runc: 1.0 release candidate breaks docker 1.11 - oci runtime error:
flag provided but not defined: -bundle
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
855208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.0.0~rc2+git20170201.133.9df8b30-1
On Mon, 26 Jun 2017 17:45:28 -0400 Antoine Beaupre
<anar...@orangeseeds.org> wrote:
> Control: fixed -1 1.0.0~rc2+git20170201.1
>
> On Fri, Feb 24, 2017 at 10:39:00PM +0100, Vincent Bernat wrote:
> > ❦ 24 février 2017 12:34 -0800, Norbert Kiesel <nkie...@gmail.com> :
> >
> > > What else can I do to get docker working again?
> >
> > You can install the one from experimental. It works fine with runc and
> > containerd from unstable. At this point, Tim should just upload it to
> > unstable.
>
> From what I can tell, this is now fixed in unstable: I was able to
> install all of this with the sid packages in stretch.
Thanks, closing the bug then with a version which existed in unstable.
Cheers,
Balint
--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
