unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Oleg Pykhalov <go.wigust@gmail.com>, 55936@debbugs.gnu.org
Subject: bug#55936: dockerd fails to start on boot
Date: Fri, 15 Jul 2022 12:20:46 +0200	[thread overview]
Message-ID: <87k08e8yo1.fsf@gnu.org> (raw)
In-Reply-To: <87wncgyb67.fsf_-_@gmail.com> (Maxim Cournoyer's message of "Wed,  13 Jul 2022 17:06:56 -0400")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> I've researched more on the topic, and it appears what I had on mind is
> rather systemd's socket *notification* (what they call 'sdNotify')
> rather than activation.  Activation is just to lazy start things... it
> probably wouldn't help here, rather it seems it'd be a bad idea, as
> realized elsewhere [0].
>
> [0]  https://github.com/containerd/containerd/issues/164#issuecomment-657536515

Currently the Shepherd implements activation as lazy start, but we
should add an option for “eager socket activation” where the daemon is
started right away.

Such activation is still useful as a synchronization mechanism: you can
tell the service is ready to serve requests as soon as the socket has
been created.

Thanks,
Ludo’.




  parent reply	other threads:[~2022-07-15 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 22:56 bug#55936: dockerd fails to start on boot Luciano Laratelli
2022-06-24  5:11 ` Maxim Cournoyer
2022-07-02 10:41 ` bug#55936: [PATCH] services: docker: Fix race condition Oleg Pykhalov
2022-07-10  5:10   ` Maxim Cournoyer
2022-07-13 21:06     ` bug#55936: dockerd fails to start on boot Maxim Cournoyer
2022-07-14  1:40       ` Maxim Cournoyer
2022-07-15 10:20       ` Ludovic Courtès [this message]
2022-07-16  1:55         ` Maxim Cournoyer

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=87k08e8yo1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=55936@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    /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).