The changes include a separate top level key named. # ^^^ on linux, no match, port is no longer open after docker-compose down. Docker Compose allows us developers to write a YAML configuration file for our. With Docker Compose v1.6.0+, there now is a new/version 2 file syntax for the docker-compose.yml file. $ docker-compose down -v -remove-orphansĬom.docke 837 brice.burgess 20u IPv6 0x57ec19a4cbc5d37d 0t0 TCP *:49892 (LISTEN) Lsof -iTCP -sTCP:LISTEN # -> shows the port ping-pong get bound to as open / listeningĭocker-compose version 1.28.5, build c4eb3a1fĬreating network "tmp_default" with the default driver The command used to stop the composition is docker-compose down -v -remove-orphans example version: "3.9" Anway, hope this is helpful to someone as google pointed me to this issue when looking for solutions. Edit: just noticed that this entire bug report was about docker, not docker-compose. When stopping a composition, bound ports remain open. It appears that the issue is resolved when upgrading to docker-compose version 1.25.0, build b42d419. ![]() ![]() ![]() This is not an issue on linux - so my guess this either has to do w/ compose or docker/for-mac. ![]() I'm using the latest docker-compose (1.28.6) and Docker Desktop 3.2.2 (on Mac OS), non experimental.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |