Replies: 3 comments
-
Whoops, it seems I was under the impression that that compose.yml declares a network for those 2 containers It seems I'm that inattentive user right now |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
I have a suggestion about a sample docker-compose shown at /configs/docker/#using-docker-socket-proxy:
Since two containers are isolated within a dedicated network, this particular port mapping is not necessary for inter-container communications to function. There is a concern that an inexperienced or inattentive user could inadvertently expose port 2375 on the host if the "127.0.0.1:" segment is lost at some point.
And we all know that kind of errors happen. For example, Portainer does not preserve the "127.0.0.1" portion of the binding when using the "Duplicate/Edit" feature.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions