Ignore missing containers when compose down/stop -p #11692
Merged
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 I did
Fix the error of docker compose down/stop with
-p
could not find <container>: not found
when there are services depend_on missing containers. The scenario is particularly likely to happen when using initial containers. docker system prune is one reason to remove init containers, for example.Related issue
fixes #11686
(not mandatory) A picture of a cute animal, if possible in relation to what you did