thatnovaguy Posted August 26, 2022 Share Posted August 26, 2022 I'm wanting to put my docker containers on a custom network so I can use the container name in place of the ip address when setting up the various arrs and other things. Once a container is moved to the new custom network it's webui becomes inaccessible. I'm not sure what I'm doing wrong or if it's something messed up within my setup. Quote Link to comment
bonienl Posted August 26, 2022 Share Posted August 26, 2022 webUI access to containers won't work with user defined custom networks. You can use bridge (e.g. br0) custom networks to put a container on a dedicated IP address. I run my own DNS server on my LAN network, which allows me to create names with associated IP addresses. Quote Link to comment
Solution thatnovaguy Posted August 26, 2022 Author Solution Share Posted August 26, 2022 13 minutes ago, bonienl said: webUI access to containers won't work with user defined custom networks. You can use bridge (e.g. br0) custom networks to put a container on a dedicated IP address. I run my own DNS server on my LAN network, which allows me to create names with associated IP addresses. NVM I sorted it. Somehow the container port got changed to match the host port so it was internally pointing to the wrong port. 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.