ci: add buildkit_config CA trust for artifactapi push #18

Merged
benvin merged 1 commits from benvin/buildx-ca-config into main 2026-08-15 18:47:21 +10:00
Member

Both artifactapi push steps use the CA-baked plugin-docker-buildx image, but buildkitd runs in its own container and does the actual push, so it needs the artifactapi CA passed via buildkit_config even though the plugin image already trusts it.

This adds settings.buildkit_config to BOTH push steps (docker-operator and docker-tsig-api), pointing the buildx docker-container builder at the in-image CA at /etc/docker/certs.d/artifactapi.k8s.syd1.au.unkin.net/ca.crt.

Proven working in jellyfin-ha v0.1.2. Does not touch the build.yaml dry-run steps.

Both artifactapi push steps use the CA-baked plugin-docker-buildx image, but buildkitd runs in its own container and does the actual push, so it needs the artifactapi CA passed via buildkit_config even though the plugin image already trusts it. This adds settings.buildkit_config to BOTH push steps (docker-operator and docker-tsig-api), pointing the buildx docker-container builder at the in-image CA at /etc/docker/certs.d/artifactapi.k8s.syd1.au.unkin.net/ca.crt. Proven working in jellyfin-ha v0.1.2. Does not touch the build.yaml dry-run steps.
unkin-agent added 1 commit 2026-08-15 18:30:57 +10:00
ci: add buildkit_config CA trust for artifactapi push
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/build Pipeline was successful
f2b7d07006
Point the buildx docker-container builder at artifactapi's in-image CA
(/etc/docker/certs.d/.../ca.crt) so buildkitd, which runs in its own
container and performs the push, trusts the registry. Applied to both
push steps (docker-operator and docker-tsig-api). Proven in jellyfin-ha
v0.1.2.
benvin merged commit 8d5a231a78 into main 2026-08-15 18:47:21 +10:00
benvin deleted branch benvin/buildx-ca-config 2026-08-15 18:47:21 +10:00
Sign in to join this conversation.