The docker client and engine both include a 'BuildTime' variable set in
their build scripts.
Overriding that to a consistent value is sufficient for them to build
reproducibly as best I can tell.
This CLI's build scripts have a mechanism for doing this. The engine has
an upstream patch (included starting with 17.07) that allows doing the
same.
This modifies the build to apply the above build patch, and set a build
time for both.
It's expected that the build time will be set by the ebuild author each
time the ebuild is modified, thus turning the 'build time' output to
really be the 'package created time', which I think is a reasonable
difference.
Accept ipvsadm on arm64
Accept newer libnl on arm64
Add ipvsadm to base
Add env file so pkg-config looks in the correct paths
Add /etc/libnl to INSTALL_MASK
Fixed lvm being out of order in INSTALL_MASK
Given our tooling, such as kola and ore, interacts with AWS, it's also
handy to have the awscli laying around to do things like emergency
cleanup, misc bash scripting, and other poking around.
LOCKUP_DETECTOR was split into HARDLOCKUP_DETECTOR and
SOFTLOCKUP_DETECTOR in 05a4a95279311c3a4633b4277a5d21cfd616c6c7.
CIFS_SMB2 was made mandatory (under CIFS) in
2a38e12053b760a8f5e85030eb89512660077c15.
kernel-2.eclass expects -rc kernels to be versioned without a patch
number, and then puts the minor version in KV_PATCH. Handle this case.
Also override the KERNEL_URI to drop the -coreos suffix.
Gentoo versioning requires a version like 4.13_rc6, but coreos-sources
unpacks to a directory named 4.13-rc6-coreos. Fix up source directory and
defconfig searches.
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
