From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#34333: Docker daemon failing to start on boot Date: Fri, 1 Mar 2019 19:00:06 +0100 Message-ID: <20190301185944.550d0ee7@scratchpost.org> 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> <87d0na3dqo.fsf@adair.io> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/aiOqmKRYltPvghPeXlnTkar"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53532) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gzmU3-0002AV-8F for bug-guix@gnu.org; Fri, 01 Mar 2019 13:02:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gzmU0-0006F4-HU for bug-guix@gnu.org; Fri, 01 Mar 2019 13:02:06 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:43237) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gzmTx-0006Ck-TE for bug-guix@gnu.org; Fri, 01 Mar 2019 13:02:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gzmTx-0001Q7-MT for bug-guix@gnu.org; Fri, 01 Mar 2019 13:02:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d0na3dqo.fsf@adair.io> 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: Allan Adair Cc: 34333@debbugs.gnu.org --Sig_/aiOqmKRYltPvghPeXlnTkar Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, On Fri, 01 Mar 2019 14:50:39 +0100 Allan Adair wrote: > After a fresh boot: >=20 > allana@guixsd ~$ docker ps > Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is th= e 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/blk= io file-system-/sys/fs/cgroup/cpu file-system-/sys/fs/cgroup/cpuset file-sy= stem-/sys/fs/cgroup/devices file-system-/sys/fs/cgroup/memory networking ud= ev). > Conflicts with (). > Will be respawned. > allana@guixsd ~$ sudo herd start dockerd > Service dockerd could not be started. > herd: failed to start service dockerd In a way that's good that this failure is reproducible so well. "herd start dockerd" would do: $(guix build docker)/bin/dockerd -p /var/run/docker.pid For debugging, can you please try invoking the latter instead of "herd start dockerd" ? After that, please try $(guix build docker)/bin/dockerd -p /var/run/docker.pid -D --Sig_/aiOqmKRYltPvghPeXlnTkar Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlx5cyYACgkQ5xo1VCww uqVnQwf+MqZ35efArpA+I0ZsCTDQvUJILKEHejP9v09Iwv+4SLOlWO2FdNIezIeW EXBL1kku14dXLGXjwEmXw1/0PKxMJF7D4ai9D3hmEy7OGYlzZk/Gr7NzJAEXECEV ap6659JTRr3TZ2t9+InD/M5+dElp3UMOpn64J/+GNT4f99LXX6xGvdlT4H3ZcFiv saHRZu+kZ3+LndUheQx/fc+nhrst/qybjGU7jjR9ZZrNqE0cM8ambDqyS0QmdF9V EOcJluHwPYX4mWUOtl/oWDz0fRm4lHlvkQWfgIavVszTyWRwXiuGctc1Gc5K96bk Z/mHba510JwjhI4JLI6gOgCZuD5/0A== =4iM2 -----END PGP SIGNATURE----- --Sig_/aiOqmKRYltPvghPeXlnTkar--