From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?=
	<bjoern.hoefling@bjoernhoefling.de>
Subject: bug#34333: Docker daemon failing to start on boot
Date: Wed, 27 Feb 2019 16:53:27 +0100
Message-ID: <20190227165327.72fc918e@alma-ubu>
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>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	boundary="Sig_/l1zWSqYI6ilwhw52IBynAQ2";
	protocol="application/pgp-signature"
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:57911)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gz1X6-0000G4-EZ
	for bug-guix@gnu.org; Wed, 27 Feb 2019 10:54:09 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gz1X4-0003Gn-EX
	for bug-guix@gnu.org; Wed, 27 Feb 2019 10:54:08 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:40626)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gz1Wz-0003Fj-NB
	for bug-guix@gnu.org; Wed, 27 Feb 2019 10:54:02 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gz1Wz-0001ND-KX
	for bug-guix@gnu.org; Wed, 27 Feb 2019 10:54:01 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.34333.B34333.15512828195249@debbugs.gnu.org>
In-Reply-To: <87imx5gvth.fsf@adair.io>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Allan Adair <allan@adair.io>
Cc: 34333@debbugs.gnu.org

--Sig_/l1zWSqYI6ilwhw52IBynAQ2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, 27 Feb 2019 15:17:14 +0100
Allan Adair <allan@adair.io> wrote:


> After a "guix system reconfigure", it works -- meaning that the
> dockerd service starts. But when booting in the future, the dockerd
> daemon never starts. I am however able to execute "sudo herd start
> dockerd" after booting because I have included dockerd in my user
> profile.  I can also "guix system reconfigure" at this point to start
> the dockerd service, but then at the next boot it will still not
> start.

I can confirm this behaviour, though I haven't yet investigated it
further.

Bj=C3=B6rn

--Sig_/l1zWSqYI6ilwhw52IBynAQ2
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXHaydwAKCRC/KGy2WT5f
/TQ4AJ420LX5z6Bc3UQOCBK9N+xK5SZw/QCdF2LPsDyAmeVanrVCz1c+UfYjf9Q=
=Ykeu
-----END PGP SIGNATURE-----

--Sig_/l1zWSqYI6ilwhw52IBynAQ2--