Repository navigation
Fix deployment migration network conflict - #41
Merged
Merged
Conversation
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
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 changed
Root cause
The live auth container owns
10.203.0.3onauth-edge.docker compose run auth ...inherited the same fixed address, so Docker rejected the migration container withAddress already in usebefore Alembic ran.Impact
The live service keeps its stable ingress address, while migration containers receive a dynamic address and can run alongside it.
Validation
docker compose -f docker-compose.yml -f docker-compose.migrate.yml config --quietipv4_addressalembic currentfrom the one-off container reached PostgreSQL and reportedd9e0f1a2b3c4 (head)