Timeline for What is the difference between ports and expose in docker-compose?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2024 at 2:13 | comment | added | Auspex | @Della Surely it's not containers "outside the specific Docker-compose file", it's containers connected (or not) to a specific network. By default, all containers in a compose file are in the same network, but "it ain't necessarily so" | |
| Jul 8, 2024 at 8:00 | comment | added | Della |
When you say world inside docker, does it include all containers running on the same host (EC2 instance), even those containers outside the specific docker-compose file?
|
|
| Apr 19, 2024 at 23:06 | history | edited | Matthias Braun | CC BY-SA 4.0 |
try to improve language, add image description
|
| Jan 11, 2024 at 8:58 | comment | added | Johan | larsks claims this is incorrect stackoverflow.com/a/65785558/3755989 | |
| Jul 13, 2023 at 19:40 | comment | added | Aditya | actually, all these days I understood this concept in reverse order thank you!! | |
| Jul 24, 2020 at 10:53 | comment | added | Reven | That's very important part: 'Activates container to listen for a specific port only from the world inside' | |
| Aug 9, 2019 at 17:40 | history | edited | steampowered | CC BY-SA 4.0 |
edited body
|
| Apr 24, 2019 at 14:02 | comment | added | Stuart Moore | Note that expose allows multiple ports - docs.docker.com/compose/compose-file/#expose - however you only supply the internal port rather than internal + external | |
| Feb 26, 2019 at 10:58 | history | answered | Mehraj Malik | CC BY-SA 4.0 |