From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 6 Dec 2018 09:49:24 +0100 Subject: [Buildroot] Docker client does not function correctly in 2018.11 In-Reply-To: References: <8dcf0b32c7fe49e8b30b10a482f3f23a@exitstrategytech.com> <5db9d4aa533e4e8590b5c33d2bb47665@exitstrategytech.com> <6e255ac5c09e4841ac67d6f383249556@exitstrategytech.com> <99kkgapwmjckouvyyw5vo6pe.1544060571584@email.android.com> Message-ID: <20181206094924.0c0737f5@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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