summaryrefslogtreecommitdiffstats
path: root/recipes-containers/runc
Commit message (Collapse)AuthorAgeFilesLines
...
* runc/containerd: use go.bbclass for dependenciesBruce Ashfield2017-04-111-2/+1
| | | | | | | Rather than explicit go-cross DEPENDS, we can inherit go.bbclass and pick up them automatically. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc-opencontainers: Update to v1.0.0-rc3Paul Barker2017-04-101-2/+9
| | | | | Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* recipes-containers: set GOROOTKhem Raj2017-03-211-1/+1
| | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc/containerd: create virtual/runc and virtual/containerdBruce Ashfield2017-02-203-8/+19
| | | | | | | | | | | | | | Since there are two implementations of runc and containerd that may not always be in sync, the docker variant, and the opencontainers variable, we create a virtual/* namespace for these components. Anything requiring runc or containerd should set a preferred provider to get the desired/tested variant. We set the default provider to the docker variants, since they are the primary use case for these components. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: uprev to version required by docker 1.13.0Mark Asselstine2017-02-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | At the moment we only use runc in conjunction with docker. In order to allow docker to function correctly we need to use the version specified in docker's vendor.conf file. Uprev runc to this version. NOTE that the docker folks have actually forked runc and I have used this fork as the SRC_URI. I could have chosen instead to use the old SRC_URI along with the fork point commit as the SRCREV, and then applied the 2 commits the docker team have added beyond the fork. I opted instead to use the fork such that 'docker info' would not complain about a version mismatch. This also makes it easier to google for issues since the commit ID matches. NOTE when we eventually have more users of runc we will have to determine a strategy to either have them all use the same version or allow for multiple versions of runc on the system. This is also true for containerd. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* go-cross: add ${TARGET_ARCH} to PNMark Asselstine2017-02-091-1/+1
| | | | | | | | | | | | Since we are building a cross tool which produces something which is ARCH specific we should stick to the <toolname>-cross-<arch> naming convention. A variant of this patch has been floating around for a while but with the changes around per recipe sysroots, distributed builds, shared builds... we are best served to adopt this convention now. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* containered|runc: override GOROOT at build timeLans Zhang2017-01-211-0/+1
| | | | | | | | Similar to commit 01aa8f1, runc and containered also need to set GOROOT explicitly. Signed-off-by: Lans Zhang <jia.zhang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* containers: uprev docker (1.12.0), runc (1.0.0-rc) and containerd (0.2.2)Bruce Ashfield2016-07-271-5/+4
| | | | | | | Bumping the version of docker and dependencies. This gets us closer to runc 1.0, which is the foundation for future OCI efforts. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Use go-osarchmap to set GOARCHPaul Barker2016-06-171-8/+3
| | | | | | | | | | | | When building for qemux86 the following error was encountered due to GOARCH being set incorrectly: compile: unknown architecture "i586" This can be fixed by using the go-osarchmap class. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: Backport fix for building against muslPaul Barker2016-06-172-0/+49
| | | | | Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* runc: initial recipeBruce Ashfield2016-05-021-0/+71
With the update to docker 1.11.x, we must also introduce runc. From the runc site: runC is a CLI tool for spawning and running containers according to the OCP specification. Containers are started as a child process of runC and can be embedded into various other systems without having to run a Docker daemon. runC is built on libcontainer, the same container technology powering millions of Docker Engine installations. Docker images can be run with runC. So not only is runc required for docker, it is useful for any system that wants to run OCP containers AND docker containers. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>