From mboxrd@z Thu Jan  1 00:00:00 1970
From: Allan Adair <allan@adair.io>
Subject: bug#34333: Docker daemon failing to start on boot
Date: Fri, 01 Mar 2019 09:58:20 +0100
Message-ID: <87pnrbotsj.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>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:59923)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gze1W-0002DB-Fm
	for bug-guix@gnu.org; Fri, 01 Mar 2019 04:00:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gze1V-0003zX-Hh
	for bug-guix@gnu.org; Fri, 01 Mar 2019 04:00:06 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:42243)
	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 1gze1T-0003yG-07
	for bug-guix@gnu.org; Fri, 01 Mar 2019 04:00:03 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gze1S-0002j3-Ob
	for bug-guix@gnu.org; Fri, 01 Mar 2019 04:00:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.34333.B34333.155143076110393@debbugs.gnu.org>
In-reply-to: <20190227163121.GA17110@jurong>
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: Andreas Enge <andreas@enge.fr>
Cc: 34333@debbugs.gnu.org, Allan Adair <allan@adair.io>

Andreas Enge writes:

> On Wed, Feb 27, 2019 at 04:53:27PM +0100, Bj=C3=B6rn H=C3=B6fling 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.
>>=20
>> I can confirm this behaviour, though I haven't yet investigated it
>> further.
>
> Could this be yet another manifestation of
>    https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D34580 ?
> Services not started on boot?
>
> Andreas

I'm not so sure. One thing that I am unable to do is "herd start
dockerd".

--=20
Allan Adair
http://allan.adair.io