[Buildroot] [External] Re: [PATCH v8 1/1] docker-engine: split docker-{cli, engine}, bump to v18.06.1-ce

Christian Stewart christian at paral.in
Fri Dec 7 22:06:05 UTC 2018

Hi Matthew,

On Wed, Nov 28, 2018 at 2:35 PM Matthew Weber <Matthew.Weber at collins.com> wrote:
> > > The one use case I have been thinking about for new projects is
> > > building the most basic possible hosting environment to manage the
> > > security footprint.  Maybe a LXC system container hosting environment
> > > or a non-systemd dockerd.  Then inside of that run a systemd based
> > > docker deployment which would be easier to swap out and do a true
> > > shared filesystem approach vs a system container......
> >
> > I think the most minimum environment would be base Buildroot with either
> > the docker-containerd / runc stack, or something like cri-o (a
> > Kubernetes minimal container runtime I am examining for use with
> > Buildroot). One thing to consider is that the Go dependencies could be
> > compiled together into a single binary, which would reduce binary
> > footprint quite a bit I think. Much of Docker / dockerd features are
> > unnecessary and can be removed as well / mapped to Buildroot options.
> >
> I noticed that flatpak now has OCI format support.  That could be an
> interesting way to go light weight without a GO dependency.....

I still think either the cri-o (your aversion to Go is noted) or
Flatpak is the right approach.

To that end I've implemented Flatpak and related dependencies in
Buildroot and have a working patchset here:


Will begin testing over the next week.

Best regards,

More information about the buildroot mailing list