Jump to content

Custom docker bridge network - containers still only connect via serverip:port not hostname


Recommended Posts

Hey guys,

 

As the title suggests, I simply cannot use http//containername:port to connect to other containers. I always have to use http://serverip:port. This happens regardless of whether I'm running docker containers from the app store, or whether I'm running compose stacks in portainer. I have made sure that the containers are on the same custom bridge network (see attached pictures), but still no dice. While things work fine with http://serverip:port, it is annoying. I also can't use the custom bridge ip assigned to each container to connect to others, it's always the serverip. Any ideas?

 

Thanks

hostnameissue.jpg

hostnameissue2.jpg

network.png

Screenshot_38.png

compose.yml

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...