chore(ci): authenticate against harbor.cryptic.systems before pulling binfmt
Build / build-arm64 (push) Failing after 3m16s
Lint Markdown files / markdown-lint (push) Successful in 13s
Build / build-amd64 (push) Failing after 1m49s

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.
This commit is contained in:
2026-09-02 20:44:09 +02:00
parent 9c667ded6a
commit 4af5fe070b
3 changed files with 51 additions and 11 deletions
+27 -7
View File
@@ -9,9 +9,7 @@ jobs:
push-arm64:
runs-on: ubuntu-latest-arm64
steps:
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
- uses: docker/setup-qemu-action@1f40c72289eff860ee54a304f1438e3cff362e0a # v4.3.0
- uses: docker/setup-buildx-action@37fe631027851001ddb9b187196cc803df7f5f0e # v4.3.0
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f # v4.6.0
with:
@@ -19,6 +17,18 @@ jobs:
username: ${{ github.repository_owner }}
password: ${{ secrets.GIT_CRYPTIC_SYSTEMS_PACKAGE_REGISTRY_TOKEN }}
- uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f # v4.6.0
with:
registry: harbor.cryptic.systems
username: ${{ secrets.HARBOR_CRYPTIC_SYSTEMS_USERNAME }}
password: ${{ secrets.HARBOR_CRYPTIC_SYSTEMS_PASSWORD }}
- uses: docker/setup-qemu-action@1f40c72289eff860ee54a304f1438e3cff362e0a # v4.3.0
with:
image: harbor.cryptic.systems/docker/tonistiigi/binfmt:latest
- uses: docker/setup-buildx-action@37fe631027851001ddb9b187196cc803df7f5f0e # v4.3.0
- name: Build and push image
run: |
TAG=$(echo ${{ github.ref_name }} | sed 's/v//gm')
@@ -35,9 +45,7 @@ jobs:
push-amd64:
runs-on: ubuntu-latest-amd64
steps:
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
- uses: docker/setup-qemu-action@1f40c72289eff860ee54a304f1438e3cff362e0a # v4.3.0
- uses: docker/setup-buildx-action@37fe631027851001ddb9b187196cc803df7f5f0e # v4.3.0
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f # v4.6.0
with:
@@ -45,6 +53,18 @@ jobs:
username: ${{ github.repository_owner }}
password: ${{ secrets.GIT_CRYPTIC_SYSTEMS_PACKAGE_REGISTRY_TOKEN }}
- uses: docker/login-action@dbcb813823bdd20940b903addbd779551569679f # v4.6.0
with:
registry: harbor.cryptic.systems
username: ${{ secrets.HARBOR_CRYPTIC_SYSTEMS_USERNAME }}
password: ${{ secrets.HARBOR_CRYPTIC_SYSTEMS_PASSWORD }}
- uses: docker/setup-qemu-action@1f40c72289eff860ee54a304f1438e3cff362e0a # v4.3.0
with:
image: harbor.cryptic.systems/docker/tonistiigi/binfmt:latest
- uses: docker/setup-buildx-action@37fe631027851001ddb9b187196cc803df7f5f0e # v4.3.0
- name: Build and push image
run: |
TAG=$(echo ${{ github.ref_name }} | sed 's/v//gm')
@@ -78,4 +98,4 @@ jobs:
--amend git.cryptic.systems/volker.raschek/bruteforce-wallet:${TAG}-amd64 \
--amend git.cryptic.systems/volker.raschek/bruteforce-wallet:${TAG}-arm64
docker manifest push git.cryptic.systems/volker.raschek/bruteforce-wallet:${TAG}
docker manifest push git.cryptic.systems/volker.raschek/bruteforce-wallet:${TAG}