MENU
Can this set of commands identify the published port(s) for a container?
Solution: `docker network inspect', `docker port'
Suggested Answer: A
Get Premium DCA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Yes, the docker port command can be used to identify the published ports for a running container. It shows the mapping between the host ports and the container's exposed ports. The docker network inspect command can also provide information about the network settings of the container, including port mappings. However, it's important to note that docker network inspect requires the network's name or ID as an argument, not the container's. Therefore, to get the network details of a specific container, you would first need to identify the network the container is connected to. These commands, when used appropriately, can help you identify the published ports for a container.
37 comments · newest first
DA
Dahlia
10 months ago
Wait, can it really do that? I thought it was just for networks.
IR
Irving
11 months ago
Definitely works, I've used it before!
AN
Angella
11 months ago
Not sure about `docker network inspect` for this.
MI
Mitsue
11 months ago
I think `docker port` is the right one for that.
LI
Lindsey
11 months ago
Yes, those commands can show published ports.
BE
Bernadine
12 months ago
I believe the answer is yes, but I can't recall if both commands are necessary or if just one will do the job.
LE
Lenna
12 months ago
I’m a bit confused. I thought `docker network inspect` was more about network settings than published ports.
MA
Mattie
12 months ago
I remember practicing a question where we had to identify container ports, and I feel like both commands might be relevant.
RO
Rodolfo
1 year ago
I think `docker port` can show the published ports, but I'm not sure about `docker network inspect`.
WI
Wilda
1 year ago
I've got this. The solution looks straightforward, and I've used those commands before. I'll apply them carefully and I'm sure I can get the right answer.
GE
Georgeanna
1 year ago
Wait, what? I'm a bit confused about how to approach this. I'll need to review my notes and make sure I understand the right steps.
JO
Josephine
1 year ago
Hmm, I'm not too sure about this. I'll have to double-check the documentation to make sure I'm using the right commands.
XE
Xenia
1 year ago
I think I can handle this one. The `docker network inspect` and `docker port` commands should give me the information I need to identify the published ports for a container.
ET
Ettie
1 year ago
Easy peasy! The solution provided looks spot on. I'm confident I can use those commands to find the published ports.
CH
Charolette
1 year ago
I'm pretty confident that the correct answer is C. Avoiding going down to operational levels of detail seems like a key principle when defining value streams.
TH
Thersa
1 year ago
Easy peasy! The bond is trading at a yield above the coupon rate, so the clean price will be below par. I'll go with option B.
GE
Georgiann
1 year ago
Hmm, I'm a bit confused about the different options here. I'll need to review the details on KMS keys and snapshot sharing.
GE
Geraldine
1 year ago
I remember practicing a question about tabs, and I think it was the Massing & Site tab. But it could also be the Insert tab!
ZO
Zona
2 years ago
Haha, I bet the person who wrote this question has been waiting to trick us with that `docker network inspect` option. Nice try, but I'm not falling for it!
CH
Chauncey
2 years ago
B) No
FA
Farrah
2 years ago
A) Yes
GE
Geoffrey
2 years ago
I'm not sure, but I'll go with option A) Yes based on Xenia and Tonette's rationale.
TO
Tonette
2 years ago
I agree with Xenia, those commands should be able to identify the published ports.
XE
Xenia
2 years ago
Yes, I think the commands 'docker network inspect' and 'docker port' can do that.
LU
Lucy
2 years ago
Can this set of commands identify the published port(s) for a container?
DE
Derrick
2 years ago
This is a classic case of 'read the question carefully'. The answer is right there in front of us - `docker port` is the way to go. No need to overthink it.
ST
Stephen
2 years ago
Wait, `docker network inspect`? I thought that was for checking the network configuration, not container ports. Good to know I was missing that one.
OL
Olen
2 years ago
I was surprised too, but `docker network inspect` is definitely useful for checking container ports.
GE
Geraldine
2 years ago
No, `docker network inspect` is not just for network configuration, it can also show container ports.
TA
Tayna
2 years ago
Yes, `docker network inspect` can help identify the published ports for a container.
HA
Han
2 years ago
I didn't know that either! Thanks for sharing, now I know how to check container ports.
KR
Kristel
2 years ago
No, `docker network inspect` is not just for checking network configuration, it can also show container ports.
SI
Simona
2 years ago
Yes, `docker network inspect` can also be used to identify the published ports for a container.
NA
Natalie
2 years ago
The `docker port` command is definitely the way to go here. I can't believe I didn't think of that sooner!
DO
Donette
2 years ago
B) No
SH
Sharan
2 years ago
The `docker port` command is definitely the way to go here. I can't believe I didn't think of that sooner!
NI
Nickie
2 years ago
A) Yes