volker.raschek
bd329a36f9
Lint Markdown files / markdown-lint (push) Successful in 11s
Release latest / push-arm64 (push) Successful in 2m10s
Release latest / push-amd64 (push) Successful in 1m11s
Release latest / push-manifest (push) Successful in 16s
Release latest / sync-to-hub-docker-io (push) Successful in 1m25s
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.
docker-compose
This project contains all sources to build the container image git.cryptic.systems/volker.raschek/docker-compose. The
primary goal of this project is to package the binary docker-compose as container image. The source code of the binary
can be found in the upstream project of docker/compose.
The workflow or how docker-compose can in general be used is documented at
docs.docker.com. Nevertheless, here are some examples of how to use the container
image.
IMAGE_VERSION=5.5.0
docker run \
--rm \
--volume "$(pwd):$(pwd)" \
--volume /var/run/docker.sock:/var/run/docker.sock \
--workdir "$(pwd)" \
"git.cryptic.systems/volker.raschek/docker-compose:${IMAGE_VERSION}" \
version