This repository has been archived by the owner on Jan 28, 2025. It is now read-only.
Sort services so that they always start in correct order #70
Conversation
This file contains 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
In older versions of docker-compose (Say 1.23), small numbers of containers get scheduled to start up in the order in which they are listed. In this case, it was trying to start up the api first, which hangs since it cannot open connections to postgres and vault. If we put the api at the bottom of the file it will always start after postgres and vault are up.
|
Why not using depends_on parameter? |
|
I didn't know that that existed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In older versions of docker-compose running on Linux (1.23), small numbers of containers get scheduled to start up in the order in which they are listed in docker-compose.yml. In this case, it was trying to start up the api first. This container hangs because it cannot open connections to postgres and vault. If we put the api at the bottom of the file it will always start after postgres and vault are up.
Other than adjusting the ordering, no other changes were made.