From: "Ludovic Courtès" <ludo@gnu.org>
To: allan@adair.io
Cc: 34333@debbugs.gnu.org
Subject: bug#34333: Docker daemon failing to start on boot
Date: Fri, 08 Feb 2019 22:55:48 +0100 [thread overview]
Message-ID: <87pns2vtaz.fsf@gnu.org> (raw)
In-Reply-To: <26bbaae65fb9ab18036684e9f676ac1e@adair.io> (allan's message of "Tue, 05 Feb 2019 11:29:59 +0000")
Hello,
allan@adair.io skribis:
> Hi, I am having an issue with the docker daemon as a service in
> guixsd. It seems that dockerd will not start on boot, but it will
> successfully start after running "guix system reconfigure".
[...]
> After booting:
>
>
>
> 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.
This is what happens at boot time:
> Feb 5 10:16:51 localhost shepherd[1]: Service containerd has been
[...]
> Feb 5 10:16:51 localhost NetworkManager[353]: <info>
> [1549358211.3005] NetworkManager (version 1.8.4) is starting... (for
> the first time)
[...]
> [1549358211.9031] manager: NetworkManager state is now
> CONNECTED_GLOBAL
> Feb 5 10:16:52 localhost dbus-daemon[350]: [system] Successfully
> activated service 'org.freedesktop.PolicyKit1'
> Feb 5 10:16:54 localhost ntpd[354]: Listen normally on 4 enp0s3
> 10.0.2.15:123
> Feb 5 10:16:54 localhost ntpd[354]: Listen normally on 5 enp0s3
> [fe80::e882:9a4a:3a68:9d76%2]:123
> Feb 5 10:16:56 localhost shepherd[1]: Service dockerd could not be
> started.
Danny, could it be that the ‘docker’ service should depend on
‘networking’?
FWIW, “make check-system TESTS=docker” passes for me.
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-02-08 21:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 11:29 bug#34333: Docker daemon failing to start on boot allan
2019-02-08 21:55 ` Ludovic Courtès [this message]
2019-02-11 10:46 ` Danny Milosavljevic
2019-02-11 13:11 ` Allan Adair
2019-02-11 14:24 ` Danny Milosavljevic
2019-02-11 17:31 ` Danny Milosavljevic
2019-02-12 9:05 ` Allan Adair
2019-02-12 17:45 ` Danny Milosavljevic
2019-02-27 14:17 ` Allan Adair
2019-02-27 15:53 ` Björn Höfling
2019-02-27 16:31 ` Andreas Enge
2019-03-01 8:58 ` Allan Adair
2019-03-01 13:09 ` Andreas Enge
2019-03-01 13:43 ` Björn Höfling
2019-03-01 13:50 ` Allan Adair
2019-03-01 18:00 ` Danny Milosavljevic
2019-03-11 8:59 ` Allan Adair
2019-03-12 19:47 ` Danny Milosavljevic
2019-03-18 10:23 ` Allan Adair
2019-03-18 10:53 ` Danny Milosavljevic
2019-03-18 11:05 ` Danny Milosavljevic
2019-03-18 13:47 ` Allan Adair
2019-03-25 21:46 ` Danny Milosavljevic
2019-03-26 14:15 ` Allan Adair
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pns2vtaz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34333@debbugs.gnu.org \
--cc=allan@adair.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).