Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 1/1] docker-engine: split docker-{cli, engine}, bump to v18.06.1-ce
Date: Tue, 13 Nov 2018 21:53:23 -0800	[thread overview]
Message-ID: <874lcki4rw.fsf@paral.in> (raw)
In-Reply-To: <CANQCQpa0SGdEHVFxn_wmKnktat18iAJ2YLXYQd+4Uqzq5GzG4A@mail.gmail.com>

Matthew,

Matthew Weber <matthew.weber@rockwellcollins.com> writes:
> I've started to test this series and wondered what the most minimal BR
> config would look like for the host /parent build?  Just systemd and
> docker-engine? Or are there dependencies on full core-utils /
> util-linux items?  I did look at your SkiffOS project and when I merge
> a config together their were a good amount of packages and a ~150MB
> rootfs.  Just curious what a minimal build might look like.

This is an interesting question. I had a quick scan of a defconfig Skiff
produces, and took some quick notes on what might be immediately
removable without consequence:

 - util-linux: fallocate, kill, line, login, more, newgrp, rfkill, setpriv, su
 - editors: nano and vim (can be removed)
 - wpa-supplicant: cli, hotspot, wps support likely can be removed
 - other utils: file, ssh server (dropbear could be used), mosh, compression tools
 - libv4l: unsure if necessary

The majority of these can be disabled from the base config fragments
here:

https://github.com/paralin/SkiffOS/tree/master/configs/skiff/standard/buildroot

They were originally included due to operational requirements / ease of
use in the early days of the project, but are probably not necessary in
a "production" image. They can certainly be removed from the base Skiff
packages, and left to developers to enable in other packages if needed.

I'll begin doing some tests of minimal images this week.

Something else to note: it's likely unnecessary to include Docker at
all, and these days Docker brings a lot of binary bloat with it. It
contains a full cluster management system (swarm) and a kubernetes
client, for example.

Some alternatives:

 - http://cri-o.io/ - container runtime interface, will add to BR
 - runc - can be used independently of Docker
 - docker-containerd - separate daemon for managing container basics
 - rkt - coreos container manager
 - libpod/podman: https://github.com/containers/libpod

I hope to add at least cri-o, rkt, and podman support to Buildroot in
the near future.

>> +sha256 47eda354afc199693aa338f5b2bb87e4511354c02561ddc6520a06d169921bdf        docker-cli-v18.06.1-ce.tar.gz
>
> Please add license file hashes for both packages.

Will include in the next revision of the series:

# docker-cli.hash
sha256	2d81ea060825006fc8f3fe28aa5dc0ffeb80faf325b612c955229157b8c10dc0  LICENSE
# docker-engine.hash
sha256	2d81ea060825006fc8f3fe28aa5dc0ffeb80faf325b612c955229157b8c10dc0  LICENSE

Thanks,
Christian

  reply	other threads:[~2018-11-14  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  3:24 [Buildroot] [PATCH v8 1/1] docker-engine: split docker-{cli, engine}, bump to v18.06.1-ce Christian Stewart
2018-11-14  3:36 ` Matthew Weber
2018-11-14  5:53   ` Christian Stewart [this message]
2018-11-15 21:30     ` Matthew Weber
2018-11-16  3:22       ` Christian Stewart
2018-11-27  3:14         ` Matthew Weber
2018-11-27  3:30           ` Christian Stewart
2018-11-28 22:35             ` [Buildroot] [External] " Matthew Weber
2018-12-07 22:06               ` Christian Stewart
2018-12-16 14:15 ` [Buildroot] " Peter Korsgaard

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=874lcki4rw.fsf@paral.in \
    --to=christian@paral.in \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox