Fix web container port #163
Merged
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
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I can't access the Pinpoint-web when I set it's port to other than 8080.
Pinpoint-web container appears to be using 8080 port as default unless set aside.
Reference: https://github.com/pinpoint-apm/pinpoint/blob/357d65d00618d448c33b179bcfd9d5ca3263881f/web/src/main/resources/application.yml#L8
However, the container port is set to WEB_SERVER_PORT in the docker-compose setting. So I modified this port to 8080.
There is no problem when using the 8080 port, but using another port causes this problem.