From: Danny Milosavljevic <dannym@scratchpost.org>
To: allan@adair.io
Cc: 34333@debbugs.gnu.org
Subject: bug#34333: Docker daemon failing to start on boot
Date: Mon, 11 Feb 2019 11:46:51 +0100 [thread overview]
Message-ID: <20190211114651.2b32e555@scratchpost.org> (raw)
In-Reply-To: <87pns2vtaz.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Fri, 08 Feb 2019 22:55:48 +0100
Ludovic Courtès <ludo@gnu.org> wrote:
> Danny, could it be that the ‘docker’ service should depend on
> ‘networking’?
Might be the case. They certainly muck around a lot with networking,
so it can't hurt to wait until host networking is set up.
I've added it--let's see.
Allan, can you guix pull and guix reconfigure and then try again?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-11 10:47 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 [this message]
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=20190211114651.2b32e555@scratchpost.org \
--to=dannym@scratchpost.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).