fix(docker): fetch dump in a build stage - #1403
Merged
Merged
Conversation
The db image build ran apt-get update on postgis/postgis:17-3.5, a Debian bullseye base whose bullseye-security Release file expired when LTS ended on 2026-08-31 - every Docker Hub autobuild since fails before downloading the dump (20.0.0 never built). Fetch and filter the dump in a buildpack-deps:curl stage instead, so the build needs no apt at all; the final image no longer carries curl or the raw dump layer. Claude-Session: https://claude.ai/code/session_0195FWjQNKqsSSeZuRyu8Lzi
Member
|
🎉 This issue has been resolved in version 20.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 participants
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.
postcodes.io.dbDocker Hub autobuild has failed since Debian bullseye LTS ended (31 Aug 2026):apt-get updateon thepostgis/postgis:17-3.5base now aborts on the expiredbullseye-securityRelease file, before the dump is even downloaded. That is whyrelease-20.0.0exists for the app image but the db image never built.