Your message dated Thu, 07 Jun 2018 19:23:50 +1000
with message-id <5624416.f1vgtIN3kY@deblab>
and subject line Done: docker build fails to run citing runc extraneous option
"-console"
has caused the Debian Bug report #881480,
regarding docker build fails to run citing runc extraneous option "-console"
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.)
--
881480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 1.13.1~ds2-3
Severity: grave
I dist-upgraded my system today and tried to do a docker build, it
fails with the error:
Incorrect Usage: flag provided but not defined: -console
... (mostly runc help message)
flag provided but not defined: -console
oci runtime error: flag provided but not defined: -console
I've seen in the past a similar issue that said to downgrade parts but
I can't see in the NEW queue anything else related to docker.io that
is not yet pushed through or I would have manually upgraded that.
As it is now it seems that docker.io is broken in unstable.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages docker.io depends on:
ii adduser 3.116
ii docker-containerd 0.2.3+git+docker1.13.1~ds1-1
ii docker-runc 1.0.0~rc2+git+docker1.13.1~ds1-2
ii golang-libnetwork 0.8.0-dev.2+git20170202.599.45b4086-3
ii iptables 1.6.1-2+b1
ii libapparmor1 2.11.1-3
ii libc6 2.24-17
ii libdevmapper1.02.1 2:1.02.145-4
ii libsqlite3-0 3.21.0-1
ii libsystemd0 235-2
ii lsb-base 9.20170808
Versions of packages docker.io recommends:
ii ca-certificates 20170717
ic cgroupfs-mount 1.4
ii git 1:2.15.0-1
ii xz-utils 5.2.2-1.3
Versions of packages docker.io suggests:
pn aufs-tools <none>
pn btrfs-progs <none>
pn debootstrap <none>
pn docker-doc <none>
pn rinse <none>
pn zfs-fuse | zfsutils <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
I'm closing this bug report as I don't recognize an actionable task for
maintainer to do. Docker don't restart daemon automatically as it may disrupt
running containers. This practical annoyance is design flaw (which "rkt"
doesn't have). Manual restart of docker may be required on upgrade.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
--
Best wishes,
Dmitry Smirnov
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
