I couldn't find a place in the Docker section to ask this question as it doesn't pertain to a specific docker, more how containers interact with each other and networking.

 

I run gluetun and run my *arr, etc programs through that docker.  One of the ports used is port 8000 seen here:

 

 

This is all on the bridge network or 192.168.1.0.  This all works fine.

 

I want to install the Spoolman docker on the br0.10 network.  It uses port 8000 that I set to 7912 in the template:

 

This work fine as, I can access it via 192.168.1.107:7912.

 

I want that to run on the br0.10 network as well, but when I set it to that network it doesn't work:

 

For other containers when I use the br0.10 it works fine.  Is this caused by the port 8000 conflicting with gluetun?  The other containers use non-coflicting ports.  Like this;

 

Any help would be appreciated.  I don't really understand all the docker networking.  I'm hoping to get Spoolman to run on the br0.10 network.

 

thanks

david

 

1 hour ago, lovingHDTV said:

Is this caused by the port 8000 conflicting with gluetun?

Probably yes. What kind of network is br0.10

1 hour ago, lovingHDTV said:

Based on the above it looks like you are trying to make Spoolman available with a dedicated IP address rather than via the host IP. If that is the intent then you can just remove the port mapping from the template and Spoolman should be accessible via port 8000 at its IP address. The port mapping function maps a container port to a port on the host system for which there can only ever be one mapping per external port. Giving a container its own IP address exposes the container directly to the network making all its ports accessible without need for mapping. 

Thank you!  I missed that when I chose br0.10 I needed to specify a static IP address.  

 

Everything up and running.

 

I don't care if it is a dedicated IP, I Just wanted it on the 192.168.10.0 subnet.

Edited February 6, 20251 yr by lovingHDTV