This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
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.
Implement printing published ports #98
Implement printing published ports #98
Changes from 2 commits
d8a38af
5effbdc
6fd290e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case it's useful, I implemented some presentation logic for ports in the CLI a while back (see docker/cli#581)
I also recently discovered that there's a weird discrepancy between services and containers when publishing port-ranges (still to investigate further);
For a service (
docker service create
);-p 8080-8090:80
means: map container port80
to ports8080 - 8090
on the hostFor a container;
-p 8080-8090:80
means: map container port80
to the first available port within8080 - 8090
I never realised this discrepancy was there tbh (as mentioned; need to investigate further if this was on purpose or an oversight)