Menu

We moved our image build to the buildx action and every release for three weeks pushed the same old image
📰

We moved our image build to the buildx action and every release for three weeks pushed the same old image

DEV Community: cicd·Sergey Shinder·about 3 hours ago
#m755ALxa
#devtocicd#devto#dev#build#docker
Long article (370 words) — no AI summary yet.
Reading 0:00
15s threshold

Our label service is built on a self-hosted runner, a long-lived virtual machine with its own Docker daemon. For two years the workflow ran docker build -t label-service:ci, a later step tagged label-service:ci with the commit SHA and pushed it to our registry, and the deploy job rolled out that tag.

In September we replaced the build step with docker/setup-buildx-action and docker/build-push-action, for the registry cache. We left the tag and push steps alone. Build, push and deploy all stayed green.

Three weeks later a fix for rotated carrier labels went out and the labels were still rotated. In the registry, the last fourteen SHA tags all pointed at the same digest.

setup-buildx-action creates a builder that uses the docker-container driver: BuildKit runs in a container of its own, and what it builds does not go into the Docker daemon's image store unless you ask. build-push-action has two inputs for that, load and push, and both default to false.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.