[Bug 1569763] [NEW] Cannot connect to the Docker daemon. Is the docker daemon running on this host?
Marius B. Kotsbak
1569763 at bugs.launchpad.net
Wed Apr 13 08:44:49 UTC 2016
Public bug reported:
The docker daemon is no longer running after upgrading to 16.04 beta:
Cannot connect to the Docker daemon. Is the docker daemon running on
this host?
$ /etc/init.d/docker restart
stop: Unknown instance:
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.178" (uid=1001 pid=11507 comm="start docker ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/upstart ")
** Affects: docker.io (Ubuntu)
Importance: Undecided
Status: New
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Tags: xenial
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1569763
Title:
Cannot connect to the Docker daemon. Is the docker daemon running on
this host?
Status in docker.io package in Ubuntu:
New
Status in upstart package in Ubuntu:
New
Bug description:
The docker daemon is no longer running after upgrading to 16.04 beta:
Cannot connect to the Docker daemon. Is the docker daemon running on
this host?
$ /etc/init.d/docker restart
stop: Unknown instance:
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.178" (uid=1001 pid=11507 comm="start docker ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/upstart ")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1569763/+subscriptions
More information about the foundations-bugs
mailing list