Bind torchserve container ports to localhost ports #2646
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.
Description
When starting torchserve inside a container, although the address configurations are set to
0.0.0.0
which is required to access torchserve from outside the container, access to torchserve in the container can be limited to localhost by binding the container ports to localhost ports as followsconfig.properties
Container ports not bound to localhost ports
Container ports bound to localhost ports
Fixes #2610
Type of change
Feature/Issue validation/testing