linux/meta-virtualization.git/recipes-containers/containerd, branch master-push

containerd: Disable for all mips machines

2018-09-25T21:38:12+00:00

containerd does not support mips since it depends on boltdb which does not support mips. Signed-off-by: He Zhe Signed-off-by: Bruce Ashfield

runc/containerd: fix build with go 1.9.x

2018-04-20T14:03:50+00:00

go 1.9.x was triggering linkage errors on some build hosts due to missing symbols. | tmp/work/core2-64-poky-linux/runc-docker/1.0.0-rc5+gitAUTOINC+4fc53a81fb-r0/recipe-sysroot/usr/lib/../lib/libc.a(dl-reloc-static-pie.o): In function `elf_mac: | /usr/src/debug/glibc/2.27-r0/git/sysdeps/x86_64/dl-machine.h:59: undefined reference to `_DYNAMIC' | tmp/work/core2-64-poky-linux/runc-docker/1.0.0-rc5+gitAUTOINC+4fc53a81fb-r0/recipe-sysroot/usr/lib/../lib/libc.a(dl-reloc-static-pie.o): In function `elf_get: | /usr/src/debug/glibc/2.27-r0/git/elf/get-dynamic-info.h:48: undefined reference to `_DYNAMIC' By ensuring that our sysroot provided go binary and build flags make it into the build enviroment we can build properly with 1.9 and 1.10 Signed-off-by: Bruce Ashfield

containerd: uprev to v1.0.2

2018-04-02T04:46:44+00:00

Uprev containerd to v1.0.2 for compatibility with recent docker (18.04+) builds. With this uprev we also significantly restructure the build to use more of the latest oe-core go build infrastructure, but non-standard parts of the build remain. We also allow containerd to be build with CGO enabled to avoid linkage errors with the oe provided go build infrastructure. Signed-off-by: Bruce Ashfield

docker/containerd: Export GOARCH to fix build in arm64

2017-10-09T16:38:45+00:00

If the GOARCH isn't set CGO took the ARCH from the host and tries to use -m64 flag that isn't available in aarch64 compiler. ... | # github.com/opencontainers/runc/libcontainer/system | aarch64-linaro-linux-gcc: error: unrecognized command line option '-m64' | # github.com/containerd/console | aarch64-linaro-linux-gcc: error: unrecognized command line option '-m64' | Makefile:60: recipe for target 'shim-static' failed ... Signed-off-by: Aníbal Limón Signed-off-by: Bruce Ashfield

containerd: uprev to latest 0.2.x

2017-07-17T18:02:50+00:00

To match the docker (moby) and runc updates, we need the latest containerd from the 0.2.x branch to work in cooperation with the other components. Note: containerd master won't currently work with docker master, but is very similar to 0.2.x. The build target varies slightly in master, but otherwise with these changes to the recipe and build steps we can switch easily when the time comes. Signed-off-by: Bruce Ashfield

runc/containerd: use go.bbclass for dependencies

2017-04-12T03:07:52+00:00

Rather than explicit go-cross DEPENDS, we can inherit go.bbclass and pick up them automatically. Signed-off-by: Bruce Ashfield

runc/containerd: create virtual/runc and virtual/containerd

2017-02-20T07:06:22+00:00

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

containerd: uprev to version required by docker 1.13.0

2017-02-15T19:58:37+00:00

Docker defines required dependency versions in its vendor.conf file. These can also be validated by running 'docker info' on the running system. In order to avoid issues, such as the current one where docker can't run containers, we need to ensure we match these versions. Uprev containerd to the version defined in docker's vendor.conf file. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

containerd: Fix build on 386

2017-02-10T21:16:55+00:00

Go only understands "386" as target arch, not "i586". Adjust this. Signed-off-by: Jan Kiszka Signed-off-by: Bruce Ashfield

go-cross: add ${TARGET_ARCH} to PN

2017-02-09T14:14:27+00:00

Since we are building a cross tool which produces something which is ARCH specific we should stick to the -cross- 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 Signed-off-by: Bruce Ashfield