From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Docker client does not function correctly in 2018.11
Date: Thu, 6 Dec 2018 09:49:24 +0100 [thread overview]
Message-ID: <20181206094924.0c0737f5@windsurf> (raw)
In-Reply-To: <CA+h8R2oK2mPefnBQ9c-jd7m4Tc7=s-0nsCV965r9DpsVTULuaA@mail.gmail.com>
Hello,
On Wed, 5 Dec 2018 17:47:05 -0800, Christian Stewart wrote:
> There is no official documentation at this point, the Docker package
> exists as a "include the Docker binaries in my target system" minimal
> option in Buildroot, and developers are currently left to decide how
> to configure it themselves.
>
> If you want to see how I use Docker and Buildroot as a reference, see
> https://github.com/paralin/SkiffOS.git - feel free to open issues
> there as well if you have Docker related questions / other
> non-Buildroot specific topics to discuss.
>
> The minimal requirements for Docker are a kernel compiled with a
> specific set of features enabled (see the Docker documentation) as
> well as some init process to start the daemon at system startup.
Perhaps we could try to improve things a little bit so that it works
better out of the box ?
If some kernel options are really absolutely needed for Docker to work,
then maybe we should make sure they are enabled: linux/linux.mk already
does that for a few packages.
Alternatively (or additionally), we can add a
package/docker-engine/docker-engine.txt file that gives some
details/suggestions on how to setup Docker in Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-06 8:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 17:31 [Buildroot] Docker client does not function correctly in 2018.11 David J. Fogle
2018-12-05 22:03 ` David J. Fogle
2018-12-05 22:39 ` Christian Stewart
2018-12-05 22:55 ` David J. Fogle
2018-12-05 23:51 ` David J. Fogle
2018-12-05 23:56 ` David J. Fogle
2018-12-06 0:37 ` Christian Stewart
2018-12-06 0:38 ` David J. Fogle
2018-12-06 0:41 ` David J. Fogle
2018-12-06 1:41 ` David J. Fogle
2018-12-06 1:47 ` Christian Stewart
2018-12-06 2:16 ` David J. Fogle
2018-12-06 2:23 ` Christian Stewart
2018-12-06 2:24 ` David J. Fogle
2018-12-06 2:36 ` David J. Fogle
2018-12-07 16:19 ` David J. Fogle
2018-12-16 14:13 ` Peter Korsgaard
2018-12-06 8:49 ` Thomas Petazzoni [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=20181206094924.0c0737f5@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.