f609f8ce1c10225edd5dd96c28e81a13aca43634
The workflows pulled tonistiigi/binfmt through an unauthenticated request, either directly from docker.io or from harbor.cryptic.systems before any credentials had been configured. Both variants are subject to upstream rate limiting and made the multi arch builds fail sporadically. The docker/login-action steps are now placed in front of docker/setup-qemu-action and docker/setup-buildx-action, and a second login against harbor.cryptic.systems was added so that the binfmt image is always pulled from the internal registry with valid credentials. Leftover setup-qemu-action and setup-buildx-action steps from the previous ordering were removed. All pinned actions were additionally bumped to their latest upstream release to remove the version drift between the repositories.
ansible
This container image can be used to execute ansible. It contains the latest versions of ansible-core, ansible-lint and python-boto3 to interact with AWS dynamic inventory.
Here is an example. The environment variables as well as the path to the playbook and inventory must of course be adapted to your own needs.
docker run \
--env AWS_ACCESS_KEY_ID \
--env AWS_SECRET_ACCESS_KEY \
--env AWS_SESSION_TOKEN \
--rm \
--volume $(pwd):$(pwd) \
--workdir $(pwd) \
git.cryptic.systems/volker.raschek/ansible:latest \
bash -c "ansible-galaxy install -r requirements.yaml && ansible-playbook -i inventories/demo.aws_ec2.yaml aws.yaml"
Languages
Makefile
93%
Shell
7%