So you’re trying to get 2 instances of qbt behind the same Gluetun vpn container?
I don’t use Qbt but I certainly have done in the past. Am I correct in remembering that in the gui you can change the port?
If so, maybe what you could do is set up your stack with 1 instance in, go into the GUI and change the port on the service to 8000 or 8081 or whatever.
Map that port in your Gluetun config and leave the default port open for QBT, and add a second instance to the stack with a different name and addresses for the config files.
Restart the stack and have 2 instances.
Has anyone run into issues with docker port collisions when trying to run images behind a bridge network (i think I got those terms right?)?
I'm trying to run the arr stack behind a VPN container (gluetun for those familiar), and I would really like to duplicate a container image within the stack (e.g. a separate download client for different types of downloads). As soon as I set the network_mode to 'service' or 'container', i lose the ability to set the public/internal port of the service, which means any image that doesn't allow setting ports from an environment variable is stuck with whatever the default port is within the application.
The only workaround i can think of is doing a local build of the image that needs duplication to allow ports to be configured from the e variables, OR run duplicate gluetun containers for each client which seems dumb and not at all worthwhile.
Have you thought about using a different client or maintainer? Hotio images may not have the same problem, or I know Linuxserver also maintains Transmission.
their documentation isn't as comprehensive as linuxserver.io, i'll probably have to just try it out and see if it works. looks like they also have one that has wireguard bundled but it's really unclear how that works