Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-07-12 Thread Robbie Harwood
Package: docker.io
Version: 1.13.1~ds1-2
Followup-For: Bug #864377

Well, perhaps.  The problem is that I can reproduce this on a fresh system
installation by just triggering a reinstall:

rharwood@seton:~$ sudo aptitude reinstall docker.io
The following packages will be REINSTALLED:
  docker.io 
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 
not upgraded.
Need to get 0 B/11.0 MB of archives. After unpacking 0 B will be used.
(Reading database ... 309020 files and directories currently installed.)
Preparing to unpack .../docker.io_1.13.1~ds1-2_amd64.deb ...
Unpacking docker.io (1.13.1~ds1-2) over (1.13.1~ds1-2) ...
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
Processing triggers for systemd (233-9) ...
Processing triggers for man-db (2.7.6.1-2) ...
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

Note that I haven't done any configuration or anything here, just installed
the package and then asked for a reinstall.

Thanks,
--Robbie

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

Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 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-libnetwork0.8.0-dev.2+git20170202.599.45b4086-1
ii  init-system-helpers  1.48
ii  iptables 1.6.1-2
ii  libapparmor1 2.11.0-6
ii  libc62.24-12
ii  libdevmapper1.02.1   2:1.02.137-2+b1
ii  libsqlite3-0 3.16.2-5
ii  libsystemd0  233-9
ii  lsb-base 9.20161125
ii  runc 1.0.0~rc2+git20170201.133.9df8b30-2

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

Versions of packages docker.io suggests:
pn  aufs-tools   
pn  btrfs-progs  
pn  debootstrap  
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information



Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-07-11 Thread Tim Rühsen
Here the work-around:

Use a different device driver, you likely use 'aufs'.

In /etc/default/docker change
DOCKER_OPTS="--storage-driver=aufs"
to
DOCKER_OPTS="--storage-driver=devicemapper"
(or whatever driver you like)

Then start apt-get upgrade again to configure docker.io:

apt-get --with-new-pkgs -f upgrade

Regards, Tim




signature.asc
Description: OpenPGP digital signature


Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-07-11 Thread Tim Rühsen
Just an idea... aufs too old (not matching the kernel version) ?

# uname -a
Linux blitz-lx 4.11.0-1-amd64 #1 SMP Debian 4.11.6-1 (2017-06-19) x86_64
GNU/Linux

# dpkg -l '*aufs*'
un  aufs-dev 
 (no description available)
ii  aufs-dkms   4.9+20161219-2 amd64
 DKMS files to build and install aufs
ii  aufs-tools  1:4.1+20161219-1   amd64
 Tools to manage aufs filesystems

# apt-cache policy aufs-dkms
aufs-dkms:
  Installed: 4.9+20161219-2
  Candidate: 4.9+20161219-2
  Version table:
 *** 4.9+20161219-2 500
500 https://ftp.de.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status




signature.asc
Description: OpenPGP digital signature


Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-07-11 Thread Tim Rühsen
On Mon, 26 Jun 2017 17:37:48 -0400 Antoine Beaupre
 wrote:
> Control: notfound -1 1.13.1~ds1-2
> Control: tags -1 unreproducible
> 
> Similarly: I installed 1.13.1~ds1-2 from sid on stretch and it installs
> fine.
> 
> Any more details on how to reproduce this? Which init system are you
> using? If you are using systemd, what does "systemctl status docker.io"
> say?

Have the same syptoms here (Debian SID amd64):

The fault seems to be "Error starting daemon: error initializing
graphdriver: driver not supported"

Any work-around is appreciated.

Here are the messages:


Setting up docker.io (1.13.1~ds1-2) ...
Job for docker.service failed because the control process exited with
error code.
See "systemctl  status docker.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Tue 2017-07-11 08:50:15
CEST; 9ms ago
 Docs: https://docs.docker.com
  Process: 7157 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS
(code=exited, status=1/FAILURE)
 Main PID: 7157 (code=exited, status=1/FAILURE)
Tasks: 19
   Memory: 43.2M
  CPU: 98ms
   CGroup: /system.slice/docker.service

Jul 11 08:50:13 blitz-lx systemd[1]: Starting Docker Application
Container Engine...
Jul 11 08:50:14 blitz-lx dockerd[7157]:
time="2017-07-11T08:50:14.086356811+02:00" level=info
msg="libcontainerd: new containerd process, pid: 7165"
Jul 11 08:50:15 blitz-lx dockerd[7157]: Error starting daemon: error
initializing graphdriver: driver not supported
Jul 11 08:50:15 blitz-lx systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Jul 11 08:50:15 blitz-lx systemd[1]: Failed to start Docker Application
Container Engine.
Jul 11 08:50:15 blitz-lx systemd[1]: docker.service: Unit entered failed
state.
Jul 11 08:50:15 blitz-lx systemd[1]: docker.service: Failed with result
'exit-code'.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit status 1




signature.asc
Description: OpenPGP digital signature


Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-06-26 Thread Antoine Beaupre
Control: notfound -1 1.13.1~ds1-2
Control: tags -1 unreproducible

On Fri, Jun 09, 2017 at 04:28:41PM -0300, Antonio Terceiro wrote:
> On Wed, 07 Jun 2017 14:19:16 -0400 Robbie Harwood  
> wrote:
> > 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
> 
> FWIW, I just upgraded from 1.13.1~ds1-1 and didn't notice any issues.

Similarly: I installed 1.13.1~ds1-2 from sid on stretch and it installs
fine.

Any more details on how to reproduce this? Which init system are you
using? If you are using systemd, what does "systemctl status docker.io"
say?

A.

-- 
On ne peut s'empêcher de vieillir, mais on peut s'empêcher de devenir
vieux.
- Henri Matisse


signature.asc
Description: PGP signature


Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-06-09 Thread Antonio Terceiro
On Wed, 07 Jun 2017 14:19:16 -0400 Robbie Harwood  
wrote:
> 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

FWIW, I just upgraded from 1.13.1~ds1-1 and didn't notice any issues.


signature.asc
Description: PGP signature


Bug#864377: docker.io: Failure to install (cannot start daemon)

2017-06-07 Thread Robbie Harwood
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-libnetwork0.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  libc62.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   
ii  btrfs-progs  4.9.1-1
ii  debootstrap  1.0.90
pn  docker-doc   
pn  rinse
pn  zfs-fuse | zfsutils  

-- no debconf information