package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Andi Chandler]

failed after apt-get dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docker.io 1.10.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 21 10:13:10 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-08-26 (603 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140826)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: docker.io
Title: package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Michael Hudson-Doyle (mwhudson)]

Well that's all fairly uninformative unfortunately. Does "systemctl status docker.service" show anything interesting?

[Andi Chandler (bing)]

See below. I have Docker installed, but don't use it on this PC.. but noticed it failed in the daily update.

# systemctl status docker.service
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2016-04-21 10:13:19 BST; 2h 9min ago
     Docs: https://docs.docker.com
  Process: 25855 ExecStart=/usr/bin/docker daemon -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE)
 Main PID: 25855 (code=exited, status=1/FAILURE)

Apr 21 10:13:19 LX-ELS05853 systemd[1]: Starting Docker Application Container Engine...
Apr 21 10:13:19 LX-ELS05853 docker[25855]: time="2016-04-21T10:13:19.800166591+01:00" level=fatal msg="Error starting daemon: er
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Apr 21 10:13:19 LX-ELS05853 systemd[1]: Failed to start Docker Application Container Engine.
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Unit entered failed state.
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Failed with result 'exit-code'.

[Tianon Gravi (tianon)]

That output looks like the actual error message is getting cut off -- "journalctl -u docker.service | tail" might give us a slightly more useful indication (at the very least, hopefully the full error message from the daemon).

[Andi Chandler (bing)]

Here you go:

root@LX-ELS05853:~# journalctl -u docker.service
-- Logs begin at Wed 2016-04-20 16:27:39 BST, end at Fri 2016-04-22
12:50:25 BST. --
Apr 21 10:13:10 LX-ELS05853 systemd[1]: Starting Docker Application
Container Engine...
Apr 21 10:13:10 LX-ELS05853 docker[25435]:
time="2016-04-21T10:13:10.305313412+01:00" level=fatal msg="Error starting
daemon: error initializing graphdriver: \"/var/lib/docker\" contains other
graphdrivers:
Apr 21 10:13:10 LX-ELS05853 systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Apr 21 10:13:10 LX-ELS05853 systemd[1]: Failed to start Docker Application
Container Engine.
Apr 21 10:13:10 LX-ELS05853 systemd[1]: docker.service: Unit entered failed
state.
Apr 21 10:13:10 LX-ELS05853 systemd[1]: docker.service: Failed with result
'exit-code'.
Apr 21 10:13:19 LX-ELS05853 systemd[1]: Starting Docker Application
Container Engine...
Apr 21 10:13:19 LX-ELS05853 docker[25855]:
time="2016-04-21T10:13:19.800166591+01:00" level=fatal msg="Error starting
daemon: error initializing graphdriver: \"/var/lib/docker\" contains other
graphdrivers:
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Apr 21 10:13:19 LX-ELS05853 systemd[1]: Failed to start Docker Application
Container Engine.
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Unit entered failed
state.
Apr 21 10:13:19 LX-ELS05853 systemd[1]: docker.service: Failed with result
'exit-code'.
Apr 21 12:26:53 LX-ELS05853 systemd[1]: Starting Docker Application
Container Engine...
Apr 21 12:26:54 LX-ELS05853 docker[1350]:
time="2016-04-21T12:26:54.837949976+01:00" level=fatal msg="Error starting
daemon: error initializing graphdriver: \"/var/lib/docker\" contains other
graphdrivers: d
Apr 21 12:26:54 LX-ELS05853 systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Apr 21 12:26:54 LX-ELS05853 systemd[1]: Failed to start Docker Application
Container Engine.
Apr 21 12:26:54 LX-ELS05853 systemd[1]: docker.service: Unit entered failed
state.
Apr 21 12:26:54 LX-ELS05853 systemd[1]: docker.service: Failed with result
'exit-code'.
Apr 21 12:27:22 LX-ELS05853 systemd[1]: Stopped Docker Application
Container Engine.
Apr 21 12:29:26 LX-ELS05853 systemd[1]: Starting Docker Application
Container Engine...
Apr 21 12:29:26 LX-ELS05853 docker[3643]:
time="2016-04-21T12:29:26.204608871+01:00" level=fatal msg="Error starting
daemon: error initializing graphdriver: \"/var/lib/docker\" contains other
graphdrivers: d
Apr 21 12:29:26 LX-ELS05853 systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Apr 21 12:29:26 LX-ELS05853 systemd[1]: Failed to start Docker Application
Container Engine.
Apr 21 12:29:26 LX-ELS05853 systemd[1]: docker.service: Unit entered failed
state.
Apr 21 12:29:26 LX-ELS05853 systemd[1]: docker.service: Failed with result
'exit-code'.
Apr 21 12:29:55 LX-ELS05853 systemd[1]: Stopped Docker Application
Container Engine.

On 21 April 2016 at 15:01, Tianon Gravi <email address hidden> wrote:

> That output looks like the actual error message is getting cut off --
> "journalctl -u docker.service | tail" might give us a slightly more
> ...

[Tianon Gravi (tianon)]

That output is still cut off, but does show the problem:

time="2016-04-21T12:26:54.837949976+01:00" level=fatal msg="Error
starting daemon: error initializing graphdriver: \"/var/lib/docker\"
contains other graphdrivers: d

We're missing the end of this log line which would tell us exactly
which other graph driver your machine has used previously that it
doesn't think it can use now -- the simplest fix would be to just "rm
-rf /var/lib/docker", but only if you don't have anything important
you've been using Docker for.

[Andi Chandler (bing)]

I've removed Docker from this box now anyway... but wanted to log the
ticket just in case it correlated with anything else.

A>

On 22 April 2016 at 15:01, Tianon Gravi <email address hidden> wrote:

> That output is still cut off, but does show the problem:
>
> time="2016-04-21T12:26:54.837949976+01:00" level=fatal msg="Error
> starting daemon: error initializing graphdriver: \"/var/lib/docker\"
> contains other graphdrivers: d
>
> We're missing the end of this log line which would tell us exactly
> which other graph driver your machine has used previously that it
> doesn't think it can use now -- the simplest fix would be to just "rm
> -rf /var/lib/docker", but only if you don't have anything important
> you've been using Docker for.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1572912
>
> Title:
> package docker.io 1.10.3-0ubuntu6 failed to install/upgrade:
> subprocess installed post-installation script returned error exit
> status 1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1572912/+subscriptions
>

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

[Expired for docker.io (Ubuntu) because there has been no activity for 60 days.]