Björn Höfling writes:
> On Fri, 1 Mar 2019 14:09:32 +0100 > Andreas Enge <andr...@enge.fr> wrote: > >> On Fri, Mar 01, 2019 at 09:58:20AM +0100, Allan Adair wrote: >> > >> > I am however able to execute "sudo herd start >> > >> > dockerd" after booting >> > >> > I'm not so sure. One thing that I am unable to do is "herd start >> > dockerd". >> >> You mean, you are not able to start it via >> sudo su - >> herd start dockerd >> ? >> >> It is normal that you cannot start services as a normal user. > > I wondered about that too. > > For me, a "sudo herd start dockerd" works. After that, I can use the > docker-cli tools to work with docker images and containers. They deploy > and run fine. > > Björn After a fresh boot: allana@guixsd ~$ docker ps Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? allana@guixsd ~$ sudo herd status dockerd Password: Status of dockerd: It is stopped. It is enabled. Provides (dockerd). Requires (containerd dbus-system elogind file-system-/sys/fs/cgroup/blkio file-system-/sys/fs/cgroup/cpu file-system-/sys/fs/cgroup/cpuset file-system-/sys/fs/cgroup/devices file-system-/sys/fs/cgroup/memory networking udev). Conflicts with (). Will be respawned. allana@guixsd ~$ sudo herd start dockerd Service dockerd could not be started. herd: failed to start service dockerd -- Allan Adair http://allan.adair.io
