From: Allan Adair <allan@adair.io>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 34333@debbugs.gnu.org, Allan Adair <allan@adair.io>
Subject: bug#34333: Docker daemon failing to start on boot
Date: Fri, 01 Mar 2019 14:50:39 +0100 [thread overview]
Message-ID: <87d0na3dqo.fsf@adair.io> (raw)
In-Reply-To: <20190301144324.75b81902@alma-ubu>
Björn Höfling writes:
> On Fri, 1 Mar 2019 14:09:32 +0100
> Andreas Enge <andreas@enge.fr> 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
>> >
>> > I'm not so sure. One thing that I am unable to do is "herd start
>> > dockerd".
>>
>> You mean, you are not able to start it via
>> sudo su -
>> herd start dockerd
>> ?
>>
>> 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örn
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:
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-system-/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
--
Allan Adair
http://allan.adair.io
next prev parent reply other threads:[~2019-03-01 13:51 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
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 [this message]
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=87d0na3dqo.fsf@adair.io \
--to=allan@adair.io \
--cc=34333@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
/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).