Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

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

Featured Replies

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

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.