All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Dan Callaghan <dan.callaghan@opengear.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH] docker: enable docker.socket instead of docker.service
Date: Fri, 5 Jun 2020 15:32:54 -0400	[thread overview]
Message-ID: <20200605193251.GA57767@gmail.com> (raw)
In-Reply-To: <20200603043245.604769-1-dan.callaghan@opengear.com>

Looks fine to me.

Merged.

Bruce

In message: [meta-virtualization][PATCH] docker: enable docker.socket instead of docker.service
on 03/06/2020 Dan Callaghan wrote:

> The docker daemon supports systemd socket activation. If we enable
> docker.socket (and not docker.service) then the daemon will be started
> when it is first used.
> 
> Signed-off-by: Dan Callaghan <dan.callaghan@opengear.com>
> ---
>  recipes-containers/docker/docker.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-containers/docker/docker.inc b/recipes-containers/docker/docker.inc
> index 32d4a2e..4bcb409 100644
> --- a/recipes-containers/docker/docker.inc
> +++ b/recipes-containers/docker/docker.inc
> @@ -49,7 +49,7 @@ PACKAGECONFIG[transient-config] = "transient-config"
>  inherit systemd update-rc.d
>  
>  SYSTEMD_PACKAGES = "${@bb.utils.contains('DISTRO_FEATURES','systemd','${PN}','',d)}"
> -SYSTEMD_SERVICE_${PN} = "${@bb.utils.contains('DISTRO_FEATURES','systemd','docker.service','',d)}"
> +SYSTEMD_SERVICE_${PN} = "${@bb.utils.contains('DISTRO_FEATURES','systemd','docker.socket','',d)}"
>  SYSTEMD_AUTO_ENABLE_${PN} = "enable"
>  
>  INITSCRIPT_PACKAGES += "${@bb.utils.contains('DISTRO_FEATURES','sysvinit','${PN}','',d)}"
> -- 
> 2.25.4
> 

> 


      reply	other threads:[~2020-06-05 19:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  4:32 [meta-virtualization][PATCH] docker: enable docker.socket instead of docker.service Dan Callaghan
2020-06-05 19:32 ` Bruce Ashfield [this message]

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=20200605193251.GA57767@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=dan.callaghan@opengear.com \
    --cc=meta-virtualization@lists.yoctoproject.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.
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.