Add note about application startup delay in Docker Compose tutorial #23621
+1
−1
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
Add clarification that the application may take 10-15 seconds to fully start after running docker compose up. This helps users understand why the app may not be immediately accessible at localhost:3000. Fixes docker#23500
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
bot
added
the
area/get-started
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.
Summary
Adds a note to the Docker Compose tutorial clarifying that the application may take 10-15 seconds to fully start after running
docker compose up -d --build.Changes
Updated step 5 in the "Start the application" section to inform users that the application may not be immediately accessible at
localhost:3000and that they should wait a moment and refresh if the page doesn't load right away.Why this change is needed
When users run
docker compose up, Docker reports containers as "Started" once they're running, but the applications inside (Node.js app and MySQL database) still need time to initialize and connect. This causes confusion for beginners who expect immediate accessibility after seeing "Container started" in the CLI output or within the GUI.Related Issue
Fixes #23500