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

Bug #1573890 reported by Jason Kane on 2016-04-23
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Undecided
Unassigned

Bug Description

Fresh install of 16.04 in a virtual box VM from the "Desktop" ISO.

Tried to install docker but it hung during the install, relevant ps fax showed:

 2033 pts/17 S+ 0:00 | \_ sudo apt install docker.io
 2034 pts/17 S+ 0:00 | \_ apt install docker.io
 5049 pts/1 Ss+ 0:00 | \_ /usr/bin/dpkg --status-fd 59 --configure bridge-utils:amd64 cgroupfs-mount:a
 5118 pts/1 S+ 0:00 | \_ /bin/sh /var/lib/dpkg/info/docker.io.postinst configure
 5172 pts/1 S+ 0:00 | \_ /bin/sh /usr/sbin/invoke-rc.d docker start
 5208 pts/1 S+ 0:00 | \_ systemctl start docker.service
 5209 pts/1 S+ 0:00 | \_ /bin/systemd-tty-ask-password-agent --watch

Presumable it is trying to prompt for a password to start the service but that is not propagating to the UI.

Killing 5208 and 5209 got me the not unexpected:

Terminated
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker.io (--configure):
 subprocess installed post-installation script returned error exit status 143
Setting up liberror-perl (0.17-1.2) ...
Setting up git-man (1:2.7.4-0ubuntu1) ...
Setting up git (1:2.7.4-0ubuntu1) ...
Setting up ubuntu-fan (0.9.0) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Errors were encountered while processing:
 docker.io
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish

Trying to install it again gives the same result (only faster).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docker.io 1.10.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: hid_generic usbhid hid psmouse e1000 ahci libahci fjes pata_acpi video
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 22 20:33:56 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 143
InstallationDate: Installed on 2016-04-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
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 143
UpgradeStatus: No upgrade log present (probably fresh install)

Jason Kane (jason-w-kane) wrote :
Download full text (3.3 KiB)

Do you have a /var/lib/docker/graphmapper file or anything like that?
On 23/04/2016 3:55 pm, "Jason Kane" <email address hidden> wrote:

> Public bug reported:
>
> Fresh install of 16.04 in a virtual box VM from the "Desktop" ISO.
>
> Tried to install docker but it hung during the install, relevant ps fax
> showed:
>
> 2033 pts/17 S+ 0:00 | \_ sudo apt install docker.io
> 2034 pts/17 S+ 0:00 | \_ apt install docker.io
> 5049 pts/1 Ss+ 0:00 | \_ /usr/bin/dpkg
> --status-fd 59 --configure bridge-utils:amd64 cgroupfs-mount:a
> 5118 pts/1 S+ 0:00 | \_ /bin/sh
> /var/lib/dpkg/info/docker.io.postinst configure
> 5172 pts/1 S+ 0:00 | \_ /bin/sh
> /usr/sbin/invoke-rc.d docker start
> 5208 pts/1 S+ 0:00 | \_
> systemctl start docker.service
> 5209 pts/1 S+ 0:00 | \_
> /bin/systemd-tty-ask-password-agent --watch
>
> Presumable it is trying to prompt for a password to start the service
> but that is not propagating to the UI.
>
> Killing 5208 and 5209 got me the not unexpected:
>
> Terminated
> invoke-rc.d: initscript docker, action "start" failed.
> dpkg: error processing package docker.io (--configure):
> subprocess installed post-installation script returned error exit status
> 143
> Setting up liberror-perl (0.17-1.2) ...
> Setting up git-man (1:2.7.4-0ubuntu1) ...
> Setting up git (1:2.7.4-0ubuntu1) ...
> Setting up ubuntu-fan (0.9.0) ...
> Processing triggers for ureadahead (0.100.0-19) ...
> Processing triggers for systemd (229-4ubuntu4) ...
> Errors were encountered while processing:
> docker.io
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> W: Operation was interrupted before it could finish
>
> Trying to install it again gives the same result (only faster).
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: docker.io 1.10.3-0ubuntu6
> ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
> Uname: Linux 4.4.0-21-generic x86_64
> NonfreeKernelModules: hid_generic usbhid hid psmouse e1000 ahci libahci
> fjes pata_acpi video
> ApportVersion: 2.20.1-0ubuntu2
> Architecture: amd64
> Date: Fri Apr 22 20:33:56 2016
> ErrorMessage: subprocess installed post-installation script returned error
> exit status 143
> InstallationDate: Installed on 2016-04-23 (0 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
> 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 143
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: docker.io (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: amd64 apport-package xenial
>
> --
> You received this bug notification because you are subscribed to
> docker.io in Ubuntu.
> https://bugs.launchpad.net/bugs/1573890
>
> Title:
> package docker.io 1.10.3-0ubuntu6 failed to install/...

Read more...

Jason Kane (jason-w-kane) wrote :

$ sudo tree /var/lib/docker/
/var/lib/docker/
├── containers
├── devicemapper
│   ├── devicemapper
│   │   ├── data
│   │   └── metadata
│   └── metadata
└── tmp

It appears to be mostly done installing where it gets stuck.

Preparing to unpack .../docker.io_1.10.3-0ubuntu6_amd64.deb ...
Unpacking docker.io (1.10.3-0ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up docker.io (1.10.3-0ubuntu6) ...
addgroup: The group `docker' already exists as a system group. Exiting.

Progress: [ 66%] [###########################################################............................]

Jason Kane (jason-w-kane) wrote :

For the hell of it I deleted /var/lib/docker/devicemapper on the off change there is a packaging issue similar to https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1569763. No change.

There is a docker service running. It doesn't work (docker ps hangs); syslog says:

Apr 22 21:25:50 Nix systemd[1]: Started Docker Application Container Engine.
Apr 22 21:25:50 Nix systemd[1]: Starting Docker Application Container Engine...
Apr 22 21:25:50 Nix docker[11685]: time="2016-04-22T21:25:50.397372552-07:00" level=error msg="'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded."
Apr 22 21:25:50 Nix kernel: [ 3621.739895] device-mapper: table: 252:0: thin-pool: unknown target type
Apr 22 21:25:50 Nix kernel: [ 3621.739899] device-mapper: ioctl: error adding target to table

Anyway -- Recent Macbook Pro, VirtualBox 5.0.16, Ubuntu 16.04 desktop ISO, sudo apt install docker.io

It looks more and more like a ubuntu apt/systemd oops than a docker specific problem.

Michael Hudson-Doyle (mwhudson) wrote :

What kernel are you running? Surely you have overlayfs available...

Jason Kane (jason-w-kane) wrote :

A "straight" click-yes-to-everything install of 16.04 from .iso on a macbook into virtual box gives you: ugg, borked up cut-n-paste.

Anyway:

4.4.0-21-generic

I don't actually care anymore; setup a machine to just run 16.04 native and got docker, compose and kubernetes working quite easily with no hassles. Something is funky in OSX+VirtualBox+16.04+Docker.

Launchpad Janitor (janitor) wrote :

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

Changed in docker.io (Ubuntu):
status: New → Confirmed
Anthony Fok (foka) wrote :

Sorry, I thought I have the same problem, i.e. Docker fails to start, in February 2014, but it turns out to be an entirely different problem due to version mismatch between docker.io and containerd. See https://bugs.debian.org/855621 "docker.io: Doesn't start: bad listen address format" for information.

per last comment, status back to new

Changed in docker.io (Ubuntu):
status: Confirmed → New
Launchpad Janitor (janitor) wrote :

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

Changed in docker.io (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.