v6.0.0-beta2
Pre-release
Pre-release
We've been dogfooding v6.0.0-beta1 for some time and are ready to make another beta release.
Known Issues
- Building docker images intermittently fails with
connection aborted
andIO ERROR
when trying to write files to the container's file system. This happens reasonably infrequently, and we recommend detecting build errors from docker and retrying, either inside your build scripts or by retrying the command step. If you are using docker compose to build images, or the docker-compose-buildkite-plugin, the exit status to retry on will be17
in most cases. - If you invoke docker compose with the
docker-compose
command, the--compatibilty
flag will be prepended for you. We still recommend you use thecli-version: 2
syntax in your Buildkite docker-compose plugin blocks, which is the equivalent of invoking docker compose with thedocker compose
command. - The ID of the
docker
group is now determined when the docker package is installed. Previously it was hard-coded to be1001
, but now it is993
, but that may change in later releases. If you rely on the GID being hard-coded to1001
in your builds, they may have permission errors. We recommend you use something like the bash syntaxgetent group docker | awk -F: '{print $3}'
to detect what the ID of thedocker
group is instead.
v6.0.0-beta2 (2023-07-17)
Changed
- Bump docker compose to v2.20.0 and buildx to v0.11.1 #1150 (@triarius)
- Reorganise build scripts to restart docker after installing qemu #1149 (@triarius)
Fixed
- Fix issues with docker-compose plugin by creating a script to prepend
--compatibility
flag to docker-compose #1148 (@triarius) subuid
andsubgid
files no longer have multiple ranges #1149 (@triarius)
Upgrading
Perform a CloudFormation stack update with the following URL:
https://s3.amazonaws.com/buildkite-aws-stack/v6.0.0-beta2/aws-stack.yml
If you want to launch a new stack, you can use this link (make sure not to use your production AWS account, create a new one for CI):