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

Christian Stewart christian at paral.in
Tue Nov 27 03:30:15 UTC 2018

Hi Matthew,

Matthew Weber <Matthew.Weber at collins.com> writes:
> I haven't got back to doing more evaluation of docker, but when I
> stopped working on things, I was able to narrow the hang down to be
> related to the initialization of random.

I have found the same. My laptop boot up would be blocked for minutes,
and it was quite annoying / concerning, but I found that when I pressed
some keys / moved the mouse the hang would go away. That would match
with a starvation of entropy in the kernel.

> 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.

Docker 2018.09 has been released, and I'm testing it now / will update
the next docker-engine build series submission to target v18.09.0.



More information about the buildroot mailing list