On Tue, Nov 01, 2016 at 08:42:00PM -0700, Tianon Gravi wrote:
> On 1 November 2016 at 05:35, Kurt Roeckx <k...@roeckx.be> 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 runc --start-timeout 2m
>
> Are you using systemd, or sysvinit? Anything interesting in the
> daemon logs? ("journalctl -u docker.service" for systemd,
> "/var/log/docker.log" for sysvinit IIRC)
For some reason I'm still using sysvinit (it never suggested to
switch to systemd, I didn't force it). I tried to look for the
log but failed to find it earlier. Anyway, it contains:
time="2016-11-01T13:19:58.780169977+01:00" level=warning msg="Your kernel does
not support cgroup memory limit"
time="2016-11-01T13:19:58.780218551+01:00" level=warning msg="Unable to find
cpu cgroup in mounts"
time="2016-11-01T13:19:58.780237393+01:00" level=warning msg="Unable to find
blkio cgroup in mounts"
time="2016-11-01T13:19:58.780255351+01:00" level=warning msg="Unable to find
cpuset cgroup in mounts"
time="2016-11-01T13:19:58.780478865+01:00" level=warning msg="mountpoint for
pids not found"
time="2016-11-01T13:19:58.780637202+01:00" level=fatal msg="Error starting
daemon: Devices cgroup isn't mounted"
I'm running linux-image-4.7.0-1-amd64 4.7.8-1
I'm guessing this is something systemd sets up, but that I might
need to manually set up if not using it?
> Also, are you in the "docker" group? (or running "docker ..." as root
> so that you have appropriate permission to talk to the socket?)
Yes.
Kurt
