ci: build and push Docker image based on Chainguard base image #2036
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What does this pull request do?
Release two flavours of Docker images:
Please note that we are going to preserve the current
Dockerfile
, so that users will still be able to build their own custom images based onAlpine
: this is needed becausedocker.elastic.co/wolfi/chainguard-base
is not a public base image, so docker build would fail for unauthenticated users.Tests
I created a feature branch
test/docker-images-wolfi
:Then I can test the release workflow without pushing any changes in production but generating docker images with the prefix
test-
and suffix if-wolfi
See https://github.com/elastic/apm-agent-python/actions/runs/9018252392
Docker images
The ones we usually release
Wolfi docker images
docker pull docker.elastic.co/observability/apm-agent-python:test-latest-wolfi