Fix port mapping syntax in Docker run command #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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
Context or Background:
Noticed an incorrect arrangement of options in the docker run command in the README.md, which could lead to confusion and unsuccessful container deployment.
Changes Made:
Corrected the order of the -d and -p flags in the docker run command.
Fixed the port mapping syntax to correctly map the host's port 33322 to the container's port 80.
Impact:
The corrected command in the README.md will now work as intended, facilitating users in correctly running the container without encountering port mapping issues.
Additional Notes:
Please ensure the specified host port (33322) does not conflict with other services on the host machine.