Thanks @kick-d, this looks fine (as discussed on IRC).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459916
Title:
Doesn't start after installation
To manage notifications about this bug go to:
Here is the diff for the docker.io.postinst between vivid and wily:
http://paste.ubuntu.com/11792608/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459916
Title:
Doesn't start after installation
** Description changed:
+ [SRU Description]
+
+ [Impact]
+ This bug affect the start of the docker daemon, as it isn't started after
installation.
+ Upgrade is broken also when using a direct backport from wily.
+
+ Some ajustment had to be done in docker.io.postinst to correct this
+ upgrade
Believed fixed in Wily, but still affects Vivid.
** Also affects: docker.io (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Believed fixed in Wily, but still affects Vivid.
** Also affects: docker.io (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
[Update]The following combinations to work.
systemd (219-7ubuntu6)
docker.io (1.5.0~dfsg1-1ubuntu2)
~# systemctl start docker
~# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset:
Me too.
workaround is:
root@ubuntu:~# apt-get update apt-get -y install docker.io
root@ubuntu:~# service docker start
root@ubuntu:~# service docker status
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset:
