From mboxrd@z Thu Jan 1 00:00:00 1970 From: Allan Adair Subject: bug#34333: Docker daemon failing to start on boot Date: Fri, 01 Mar 2019 14:50:39 +0100 Message-ID: <87d0na3dqo.fsf@adair.io> References: <26bbaae65fb9ab18036684e9f676ac1e@adair.io> <87pns2vtaz.fsf@gnu.org> <20190211114651.2b32e555@scratchpost.org> <20190211183155.30861768@scratchpost.org> <8a67633984fd5547e69b09fff29223ba@adair.io> <20190212184517.77edfb58@scratchpost.org> <87imx5gvth.fsf@adair.io> <20190227165327.72fc918e@alma-ubu> <20190227163121.GA17110@jurong> <87pnrbotsj.fsf@adair.io> <20190301130932.GA1867@jurong> <20190301144324.75b81902@alma-ubu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:60564) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gziZ7-0005f2-Ns for bug-guix@gnu.org; Fri, 01 Mar 2019 08:51:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gziZ5-0005Ez-UP for bug-guix@gnu.org; Fri, 01 Mar 2019 08:51:05 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:42393) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gziZ3-0005Dt-Qu for bug-guix@gnu.org; Fri, 01 Mar 2019 08:51:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gziZ3-0003no-P6 for bug-guix@gnu.org; Fri, 01 Mar 2019 08:51:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <20190301144324.75b81902@alma-ubu> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= Cc: 34333@debbugs.gnu.org, Allan Adair Bj=C3=B6rn H=C3=B6fling writes: > On Fri, 1 Mar 2019 14:09:32 +0100 > Andreas Enge 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=20=20 >> >=20 >> > I'm not so sure. One thing that I am unable to do is "herd start >> > dockerd".=20=20 >>=20 >> You mean, you are not able to start it via >> sudo su - >> herd start dockerd >> ? >>=20 >> 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=C3=B6rn 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:=20 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-syst= em-/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 --=20 Allan Adair http://allan.adair.io