all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Allan Adair <allan@adair.io>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 34333@debbugs.gnu.org, Allan Adair <allan@adair.io>
Subject: bug#34333: Docker daemon failing to start on boot
Date: Wed, 27 Feb 2019 15:17:14 +0100	[thread overview]
Message-ID: <87imx5gvth.fsf@adair.io> (raw)
In-Reply-To: <20190212184517.77edfb58@scratchpost.org>


Hey Danny.

I'm curious to know if the dockerd service type works for you. It does
not work for me, but maybe I am doing something wrong. Below is my
current config.scm:

(use-modules (gnu)
             (gnu system nss)
	     (gnu services))
(use-service-modules desktop docker)
(use-package-modules certs gnome)

(operating-system
 (host-name "guixsd")
 (timezone "Europe/Oslo")
 (locale "en_US.utf8")

  (bootloader (bootloader-configuration
               (bootloader grub-bootloader)
               (target "/dev/sda")))

  (file-systems (cons (file-system
		       (device (file-system-label "my-root"))
		       (mount-point "/")
		       (type "ext4"))
                      %base-file-systems))

  (users (cons (user-account
                (name "allana")
                (group "users")
                (supplementary-groups '("wheel"
					"docker"
					"netdev"
                                        "audio"
					"video"))
                (home-directory "/home/allana"))
               %base-user-accounts))

  ;; This is where we specify system-wide packages.
  (packages (cons* nss-certs         ;for HTTPS access
                   gvfs              ;for user mounts
                   %base-packages))

  (services (cons* (console-keymap-service "no-latin1")
                   (gnome-desktop-service)
		   (service docker-service-type)
                   %desktop-services))

  ;; Allow resolution of '.local' host names with mDNS.
  (name-service-switch %mdns-host-lookup-nss))


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.


Danny Milosavljevic writes:

> Hi Allan,
>
> On Tue, 12 Feb 2019 09:05:10 +0000
> Allan Adair <allan@adair.io> wrote:
>
>> On 2019-02-11 17:31, Danny Milosavljevic wrote:
>> > Hi Allan,
>> > 
>> > I've added some more requirements--let's see.
>> > 
>> > Can you guix pull and guix reconfigure and then try again once more?  
>> 
>> Still no luck. Do you face the same issue?
>
> I don't know since my machine has not finished updating after the
> recent staging to master merge.


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

  reply	other threads:[~2019-02-27 14: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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87imx5gvth.fsf@adair.io \
    --to=allan@adair.io \
    --cc=34333@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.