buildkite/elastic-ci-stack-for-aws v6.0.0-beta2 on GitHub

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 and IO 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 be 17 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 the cli-version: 2 syntax in your Buildkite docker-compose plugin blocks, which is the equivalent of invoking docker compose with the docker compose command.
The ID of the docker group is now determined when the docker package is installed. Previously it was hard-coded to be 1001, but now it is 993, but that may change in later releases. If you rely on the GID being hard-coded to 1001 in your builds, they may have permission errors. We recommend you use something like the bash syntax getent group docker | awk -F: '{print $3}' to detect what the ID of the docker group is instead.

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)

Fix issues with docker-compose plugin by creating a script to prepend --compatibility flag to docker-compose #1148 (@triarius)
subuid and subgid files no longer have multiple ranges #1149 (@triarius)

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):