-
Notifications
You must be signed in to change notification settings - Fork 642
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Always include Ports within inspect response
Related to #3310 New behavior will always initialize a NetworkSettings entity within the inspect response. If the target container does not exist, the NetworkSettings will be full of "zero-value" members. If the target container is active, but ports were not published, then the Ports key of NetworkSettings will have an empty structure value. If the target container is active and ports were published, then the Ports key of NetworkSettings will have populated values. Signed-off-by: Sam Chew <[email protected]>
- Loading branch information
1 parent
74f2755
commit 054e158
Showing
4 changed files
with
22 additions
and
12 deletions.
There are no files selected for viewing
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
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
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
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