GNU bug report logs - #55936
dockerd fails to start on boot

Previous Next

Package: guix;

Reported by: Luciano Laratelli <luciano <at> laratel.li>

Date: Mon, 13 Jun 2022 00:22:02 UTC

Severity: normal

Merged with 38432

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#38432: closed (dockerd is not started automatically)
Date: Thu, 14 Jul 2022 01:42:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 13 Jul 2022 21:40:53 -0400
with message-id <877d4g1nfe.fsf <at> gmail.com>
and subject line Re: bug#55936: dockerd fails to start on boot
has caused the debbugs.gnu.org bug report #55936,
regarding dockerd is not started automatically
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
55936: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55936
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: andreoss <at> SDF.ORG
To: bug-guix <at> gnu.org
Subject: dockerd is not started automatically
Date: Fri, 29 Nov 2019 22:06:10 +0000
When defined in /etc/config.scm as the manual suggests[1]
>    (service docker-service-type)

dockerd is not started with other services.
It could be started manually by
$ herd start dockerd

[1] https://guix.gnu.org/manual/en/html_node/Miscellaneous-Services.html


[Message part 3 (message/rfc822, inline)]
From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Oleg Pykhalov <go.wigust <at> gmail.com>
Cc: 55936-done <at> debbugs.gnu.org
Subject: Re: bug#55936: dockerd fails to start on boot
Date: Wed, 13 Jul 2022 21:40:53 -0400
Hi Oleg,

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> Hi Oleg,
>>
>> Oleg Pykhalov <go.wigust <at> gmail.com> writes:
>>
>>> Fixes <https://issues.guix.gnu.org/38432>.
>>>
>>> * gnu/packages/patches/containerd-create-pid-file.patch: New file.
>>> * gnu/local.mk (dist_patch_DATA): Add this.
>>> * gnu/packages/docker.scm (containerd)[source]: Add this patch.
>>> * gnu/services/docker.scm
>>> (containerd-shepherd-service): Add #:pid-file and #:pid-file-timeout.
>>> * gnu/services/docker.scm (docker-shepherd-service): Add --containerd flag.
>>
>> Thanks for this, it looks promising!

[...]

> All that to say that I shall be reviewing your patches shortly :-).

Now done; it all looks good to me!  I've run the docker system test, and
installed it on my machine, rebooted, confirmed it was up, restarted
containerd a couple times and checked the PID content matched its actual
PID, and it seems to behave as expected!

Pushed as b33e1a183f6756514e6b6a3b84054a232dbddad4.

Thank you!

Maxim


This bug report was last modified 2 years and 315 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.