hotio Posted December 27, 2019 Share Posted December 27, 2019 When using a custom bridge network to seperate containers from eachother, there's no field for the container port when mapping a port to the host. The default bridge network doesn't allow to reference other containers by their name. A custom bridge network is used in many cases to solve this when multiple containers need to communicate. See this thread, for more info/screenshots: Quote Link to comment
bonienl Posted December 27, 2019 Share Posted December 27, 2019 I made a change to support this. It will be available in the next version. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.