Your message dated Sat, 09 Jun 2018 13:50:36 +1000
with message-id <1892490.vch5eM3s3S@deblab>
and subject line Done: docker.io: Failure to install (cannot start daemon)
has caused the Debian Bug report #864377,
regarding docker.io: Failure to install (cannot start daemon)
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.)


-- 
864377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docker.io
Version: 1.13.1~ds1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

During a system upgrade, I got the following:

Setting up docker.io (1.13.1~ds1-2) ...
[....] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start"
failed.
dpkg: error processing package docker.io (--configure):

Followed by, at the end:

Errors were encountered while processing:
 docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up docker.io (1.13.1~ds1-2) ...
[....] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" 
failed.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 docker.io

I grepped logs for error, but don't see anything related, and they're so
incredibly verbose as to be useless.

Thanks,
--Robbie

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

Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages docker.io depends on:
ii  adduser              3.115
ii  containerd           0.2.3+git20170126.85.aa8187d~ds1-1
ii  golang-libnetwork    0.8.0-dev.2+git20170202.599.45b4086-1
ii  init-system-helpers  1.48
ii  iptables             1.6.0+snapshot20161117-6
ii  libapparmor1         2.11.0-3
ii  libc6                2.24-11
ii  libdevmapper1.02.1   2:1.02.137-2
ii  libsqlite3-0         3.16.2-4
ii  libsystemd0          232-25
ii  lsb-base             9.20161125
ii  runc                 1.0.0~rc2+git20170201.133.9df8b30-1

Versions of packages docker.io recommends:
ii  ca-certificates  20161130+nmu1
ii  cgroupfs-mount   1.4
ii  git              1:2.13.1+next.20170605-1
ii  xz-utils         5.2.2-1.2+b1

Versions of packages docker.io suggests:
pn  aufs-tools           <none>
ii  btrfs-progs          4.9.1-1
ii  debootstrap          1.0.90
pn  docker-doc           <none>
pn  rinse                <none>
pn  zfs-fuse | zfsutils  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Package: docker.io
Version: 1.13.1~ds2-3

I believe this problem has been fixed in version 1.13.1~ds2-3.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 864...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

-- 
Best wishes,
 Dmitry Smirnov

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to