Your message dated Mon, 21 Nov 2016 21:40:49 -0500 with message-id <CAO6P2QRS4E46ob5s-ULDKkpnJUHCgKtR=7wglzvdtuos4ek...@mail.gmail.com> and subject line Re: Bug#842806: docker.io: Can't connect to the daemon has caused the Debian Bug report #842806, regarding docker.io: Can't connect to the daemon to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 842806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842806 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---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_BROADCAST, [1], 4) = 0 connect(3, {sa_family=AF_UNIX, sun_path="/var/run/docker.sock"}, 23) = -1 ECONNREFUSED (Connection refused) close(3) = 0 futex(0xc820028d08, FUTEX_WAKE, 1) = 1 write(2, "Cannot connect to the Docker dae"..., 80Cannot connect to the Docker daemon. Is the docker daemon running on this host? ) = 80 exit_group(1) = ? 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 runc --start-timeout 2m Kurt
--- End Message ---
--- Begin Message ---Closing this bug. The bug appears to be that the system in question didn't have cgroups mounted, and wasn't otherwise configured in expert mode correctly. Given that the cgroups package that wasn't installed is to be found together with Docker in all but unusual installations, I'm not generally willing to move that relation to Depends. It's perfectly fine to configure it manually (I have, certainly). Please re-open if installing the packages in Recommends doesn't solve it (of course, removing any ones you will have otherwise removed intentionally). Cheers, Paul On Mon, Nov 21, 2016 at 7:18 PM, Tianon Gravi <[email protected]> wrote: > severity 842806 important > thanks > > On 21 November 2016 at 00:18, Kurt Roeckx <[email protected]> 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? This sounds like >>> a system configuration issue, not necessarily a package-level issue, >>> so the most we could do is maybe fuddle Depends or add a blurb in >>> README.Debian. :( >> >> Yes, sounds fine for me. > > Thanks! <3 > > > ♥, > - Tianon > 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4 -- :wq
--- End Message ---
