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

[Matthew Weber]

Christian,

On Thu, Nov 15, 2018 at 9:22 PM Christian Stewart <christian at paral.in> wrote:
>
> Hi Matthew,
>
> Matthew Weber <matthew.weber at rockwellcollins.com> writes:
> > I did find that the dockercli just hangs when I call it, however I
> > check and the daemon is running.  I'll see if I can get more debug
> > (strace, etc).
>
> The CLI itself is fine, but the daemon sometimes hangs on startup. I
> have noticed this problem on my laptop as well (x86) so it's not
> specific to this build or environment, it seems.
>
> The daemon will be called, but will not log anything, and basically hang
> for sometimes minutes. I try restarting it a few times, but that doesn't
> seem to work. If I wait, it usually starts up eventually.
>
> Most of the time the daemon starts immediately, but something seems to
> trigger this hang.
>
> Once the daemon is running and logging messages, the CLI is responsive.
>
> It will probably require a strace to figure out why Docker is hanging on
> startup like this.

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.

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

Cool.

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

> >
> > Are any of those OCI compliant and not written in GO? :-)
>
> I haven't seen a OCI compliant runtime that is not Go, yet.
>
> Best,
> Christian
>

Matt