Bug#842806: docker.io: Can't connect to the daemon

2016-11-22 Thread Kurt Roeckx
On Mon, Nov 21, 2016 at 04:18:44PM -0800, Tianon Gravi wrote: > severity 842806 important > thanks > > On 21 November 2016 at 00:18, Kurt Roeckx wrote: > > It's not installed. > > So, does installing "cgroupfs-mount" (and making sure the "service" is > started from its init script) fix the issue

Bug#842806: docker.io: Can't connect to the daemon

2016-11-21 Thread Tianon Gravi
severity 842806 important thanks On 21 November 2016 at 00:18, Kurt Roeckx wrote: > It's not installed. So, does installing "cgroupfs-mount" (and making sure the "service" is started from its init script) fix the issue with Docker? :) >> Any objections to lowering the severity of this bug? Thi

Bug#842806: docker.io: Can't connect to the daemon

2016-11-21 Thread Kurt Roeckx
On Sun, Nov 20, 2016 at 07:10:43PM -0800, Tianon Gravi wrote: > On 2 November 2016 at 00:25, Kurt Roeckx wrote: > > I'm guessing this is something systemd sets up, but that I might > > need to manually set up if not using it? > > Ah yeah, sounds like it -- did you install recommends when installi

Bug#842806: docker.io: Can't connect to the daemon

2016-11-20 Thread Tianon Gravi
On 2 November 2016 at 00:25, Kurt Roeckx wrote: > I'm guessing this is something systemd sets up, but that I might > need to manually set up if not using it? Ah yeah, sounds like it -- did you install recommends when installing docker.io? That should've pulled in the "cgroupfs-mount" package, wh

Bug#842806: docker.io: Can't connect to the daemon

2016-11-02 Thread Kurt Roeckx
On Tue, Nov 01, 2016 at 08:42:00PM -0700, Tianon Gravi wrote: > On 1 November 2016 at 05:35, Kurt Roeckx wrote: > > The file /var/run/docker.sock seems to exist, is created when it starts, > > but it really seems to be listening to an other socket. > > > > The process that's running shows: > > con

Bug#842806: docker.io: Can't connect to the daemon

2016-11-01 Thread Tianon Gravi
On 1 November 2016 at 05:35, Kurt Roeckx wrote: > The file /var/run/docker.sock seems to exist, is created when it starts, > but it really seems to be listening to an other socket. > > The process that's running shows: > containerd -l /var/run/docker/libcontainerd/docker-containerd.sock --runtime

Bug#842806: docker.io: Can't connect to the daemon

2016-11-01 Thread Kurt Roeckx
Package: docker.io Version: 1.11.2~ds1-6 Severity: serious Hi, I just installed docker and it doesn't seem to be working properly, claiming it's not running. When I run "docker info" strace is showing: socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3 setsockopt(3, SOL_SOCKET, SO_BR