[meta-virtualization] [PATCH 0/2] get docker working again (broken by per recipe sysroots)

[Bruce Ashfield]

Following up to the list. I did finally merge this change after creating a
virtual/run
and virtual/containerd namespace for these two packages.

I've made the default preferred provider to be runc-docker, but for someone
that wants
to build the tip of the opencontainers tree, there is also a
runc-opencontainers. A
similar split exists within containerd.

Once docker and the opencontainer equivalent become one, I can undo the
virtual/*
namespace changes.

Bruce

On Fri, Feb 10, 2017 at 10:44 AM, Mark Asselstine <
mark.asselstine at windriver.com> wrote:

>
> By uprev'ing runc and containerd to the versions specified by docker's
> vendor.conf file we are able to get the docker runtime back to a fully
> functional state (ie. it now passes some basic usecases)
>
> This series is applied on top of the commit sent by Jan Kiszka
> [containerd: Fix build on 386] but should apply with our without that
> merged.
>
> It is highly unfortunate that docker is forking runc. Although we only
> have docker using runc at the moment this has the potential to cause
> issues if/when we get other runc users integrated.
>
> With these changes we can now run docker pull, docker run, docker
> images, docker ps -a,... successfully. Running 'docker run
> hello-world' produces the expected results:
>
> ----
>   Hello from Docker!
>   This message shows that your installation appears to be working
> correctly.
>
>   To generate this message, Docker took the following steps:
>   1. The Docker client contacted the Docker daemon.
>   2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
>   3. The Docker daemon created a new container from that image which runs
> the
>      executable that produces the output you are currently reading.
>   4. The Docker daemon streamed that output to the Docker client, which
> sent it
>      to your terminal.
>
>   To try something more ambitious, you can run an Ubuntu container with:
>   $ docker run -it ubuntu bash
>
>   Share images, automate workflows, and more with a free Docker ID:
>   https://cloud.docker.com/
>
>   For more examples and ideas, visit:
>   https://docs.docker.com/engine/userguide/
> ----
>
> Running 'docker info' we also see that there is no longer a mismatch
> reported for these dependencies.
>
> Mark
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-virtualization/attachments/20170221/0081644c/attachment.html>