volker.raschek
55045e178f
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.
bind9-docker
This project contains all sources to build the container image
git.cryptic.systems/volker.raschek/bind9. The primary goal of the image is only
to start a simple bind9 dns server.
The configuration files must be manually mounted into the container.
Usage
Mount your bind9 configuration to /etc/bind like to following example.
docker run \
--detach \
--rm \
--publish 53:53/tcp \
--publish 53:53/udp \
--volume <config/path>:/etc/bind \
git.cryptic.systems/volker.raschek/bind9
Build image manually
To build the images manually check out the
repository with git and use
the make command to build the container images.
make container-image/build