volker.raschek
adcbf90d96
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.
rpm-builder
This project contains only build sources for the container image git.cryptic.systems/volker.raschek/rpm-builder. The
upstream project ist hosted on github.
Usage
Package an example application like my-demo-application via the following example command.
$ docker run \
--workdir /workspace \
--volume ${PWD}/workspace:rw \
--rm \
git.cryptic.systems/volker.raschek/rpm-builder:latest \
--arch=x86_64 \
--epoch=0 \
--version=0.1.0 \
--release=1 \
--license="Apache 2.0" \
--name my-demo-application \
--dir installDir:/ \
--out /workspace/my-demo-application.rpm \
.
You get on overview of all possible sub commands via --help or visit the
documentation.
$ docker run \
--rm \
git.cryptic.systems/volker.raschek/rpm-builder:latest \
--help