🐳 Migrate imagemagick and devenv images to DHI [2/3]#10733
Open
bameda wants to merge 1 commit into
Open
Conversation
penpot-triage
Bot
added
the
needs triage
bameda
changed the title
bameda
force-pushed
the
bameda-dhi-migration-imagemagic-devenv
branch
from
July 17, 2026 09:27
2b60234 to
b72274e
Compare
Move docker/imagemagick/Dockerfile and docker/devenv/Dockerfile from ubuntu:26.04 to Docker Hardened Images (Debian 13 / trixie). imagemagick gets a true non-dev runtime with its shared libraries vendored via ldd; devenv keeps the -dev tag as its final image since it's an interactive development container, not a production artifact.
bameda
force-pushed
the
bameda-dhi-migration-imagemagic-devenv
branch
from
July 17, 2026 09:41
b72274e to
de414a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Ticket
#10720
Summary
provenance: mode=maxandsbom: trueto everydocker/build-push-actionstep in the workflows. These already push to a registry(
push: true), which is a requirement for attestations to attach at all.docker/build-push-actionhas supported this since v4; we're already onv7, so no action version bump needed.