Docs/docker: clarify manual cleanup for shared docker services #48997
+4
−0
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
spring-projects-issues
added
the
status: waiting-for-triage
ZacharyScheer16
force-pushed
the
docs/docker-compose-cleanup-note
branch
from
4271676 to
85aea52
Compare
Signed-off-by: Zachary Scheer <zscheer00@gmail.com>
ZacharyScheer16
force-pushed
the
docs/docker-compose-cleanup-note
branch
from
85aea52 to
f9724d0
Compare
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.
Description
This PR enhances the Docker Compose "How-to" guide by clarifying how to properly clean up shared services.
Changes:
Added a [NOTE] block to the sharing-services section.
Clarified that while docker compose stop halts containers, docker compose down should be used to fully remove containers, networks, and anonymous volumes.
Why this is useful: The current documentation mentions start-only lifecycle management for shared services and notes that services remain running after the application stops. While it suggests docker compose stop for manual cleanup, beginners often encounter "stale" container issues if networks and volumes aren't also cleared. Explicitly mentioning docker compose down provides a completer and more modern workflow for local development.