chore(docker): move runtime images off end-of-life alpine 3.19 - #571
Open
0xrlawrence wants to merge 1 commit into
Open
chore(docker): move runtime images off end-of-life alpine 3.19#5710xrlawrence wants to merge 1 commit into
0xrlawrence wants to merge 1 commit into
Conversation
Both runtime stages pin alpine:3.19, which passed end of community support and no longer receives security patches, so the shipped image accumulates unfixed CVEs in the base layer. Bumped to alpine:3.22, which is still supported. The runtime layer only installs pigz and ca-certificates, so there is no version-sensitive surface here. Not changed, but worth a maintainer decision: neither Dockerfile declares a USER, so the node runs as root. Fixing that is not a one-line change, because .docker/compose.yaml mounts the chain data at /root/.canopy — the data directory would have to move and every volume mapping would have to move with it. Left as a follow-up rather than bundled here. Caveat: I could not build these images locally (no Docker in my environment), so this is an inspection-only change. Worth a CI build before merge.
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.
Description
Both runtime stages pin
alpine:3.19, which has passed end of community support and no longer receives security patches, so the shipped image accumulates unfixed CVEs in its base layer.Changes Made
Dockerfileand.docker/Dockerfile:alpine:3.19->alpine:3.22.The runtime layer only installs
pigzandca-certificates, so there is no version-sensitive surface here.Not changed — needs a maintainer decision
Neither Dockerfile declares a
USER, so the node runs as root. That is worth fixing, but it is not a one-line change:.docker/compose.yamlmounts chain data at/root/.canopy, so the data directory would have to move and every volume mapping would have to move with it. I left it out rather than bundling an untested permissions change here — happy to open a follow-up if you want it.Caveat
I could not build these images locally (no Docker in my environment), so this is an inspection-only change. Worth a CI build before merge.
🤖 Generated with Claude Code