All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Antliff <David.Antliff@Aviatnet.com>
To: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Docker init script possibly uses wrong invocation?
Date: Thu, 2 Aug 2018 04:04:31 +0000	[thread overview]
Message-ID: <1533182670806.88977@Aviatnet.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

I've installed the "docker" (docker_git.bb) recipe in my ARM64 yocto image, from meta-virtualization 1e67a44 (24 July).


I note that it installed /etc/init.d/docker.init, however this fails to start the daemon.


The script runs `/usr/bin/docker daemon ...` however this command is not recognised by this program:


# /usr/bin/docker daemon
docker: 'daemon' is not a docker command.

Instead, /usr/bin/dockerd run manually seems to do something more useful:
?
# /usr/bin/dockerd
INFO[2018-08-02T04:05:04.144036840Z] libcontainerd: started new docker-containerd process  pid=4643
INFO[0000] starting containerd                           module=containerd revision=cfd04396dc68220d1cecbe686a6cc3aa5ce3667c.m version=v1.0.2.m
...

I've noticed that docker.service also uses this invocation:

https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-containers/docker/files/docker.service

This makes me wonder if I've misconfigured something, or am I unlucky in my timing such that docker-from-git has changed its behaviour in this area very recently?

--
David.






[-- Attachment #2: Type: text/html, Size: 2107 bytes --]

             reply	other threads:[~2018-08-02  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02  4:04 David Antliff [this message]
2018-08-03  2:41 ` Docker init script possibly uses wrong invocation? Bruce Ashfield
2018-08-03  2:47   ` EXTERNAL: " David Antliff

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=1533182670806.88977@Aviatnet.com \
    --to=david.antliff@aviatnet.com \
    --cc=meta-virtualization@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.