This adds libltdl, which is a requirement of Docker's pkcs11-helper
bindings. The library was not installed in the OS image, so it was
just added to the Docker torcx image. It can be dropped from the
torcx image if anything else ever pulls it into the OS image.
This switches to the new Docker CE repo structure. It points to
the docker/docker-ce GitHub repo directly now, not the CoreOS fork.
The cros_workon code was dropped, so we are building unmodified
upstream releases now. If fixes need to be backported, patch files
can just be added to the PATCHES array since this uses EAPI=6.
LDFLAGS are tacked onto the -extldflags option to support torcx. A
special RPATH is added for torcx support, which is passed through
the LDFLAGS environment variable. The value is applied along with
the "hardened" USE flag's options, so note that torcx will not work
if that flag is disabled.
This takes the old app-emulation/runc ebuild and syncs it with
Gentoo. The only differences from Gentoo's rc3_p20170607 are now:
1. Use of the CoreOS Go eclasses
2. Addition of src_unpack to set up a Go workspace from the above
3. Dropping src_prepare to prevent hiding the commit ID
4. Carrying over a patch from the previous package
5. Adding the "selinux" USE flag
6. Dropping "-i" from "go build" to fix arm64 builds
This adds "hardened" LDFLAGS to the build, and it also bumps the Go
version to 1.8 to match the containerd Dockerfile.
The only differences from the upstream 0.2.9 ebuild are now:
1. Use of the CoreOS Go eclasses
2. Addition of src_unpack to set up a Go workspace from the above
3. Inclusion of the containerd.service unit
This shouldn't affect the SDK or the OS image, but ensures that debug
symbols are available from the binary package.
vmlinux is installed to:
/usr/lib/debug/usr/boot/vmlinux-<version>
vdso binaries are installed to:
/usr/lib/debug/usr/lib/modules/<version>/vdso/
A symlink is created:
/usr/lib/debug/usr/lib/modules/<version>/vmlinux ->
../../../boot/vmlinux-<version>
This shouldn't affect the SDK or the OS image, but ensures that debug
symbols are available from the binary package.
Modules are installed into:
/usr/lib/debug/usr/lib/modules/<version>/kernel/
This complements dev-db/etcd with USE="-etcdctl"
See https://github.com/coreos/bugs/issues/1717 for the motivation for
providing etcdctl as a separate package with a newer version.
This paves the way to including the etcdctl binary from another package.
See https://github.com/coreos/bugs/issues/1717 for some context around
this.
As discussed on that issue, a long term solution here might be torcx.
However, I don't think we need to actually wait for torcx to do this
since the etcd3 cli is meant to be perfectly backwards compatible.
This will also allow our docs around using `etcd-member.service` to be
more readable/usable, since right now the docs don't have an easy way to
talk to the etcd cluster from a Contaienr Linux machine.
