May 12, 20251 yr Community Expert Is there anything new in Unraid 7.1.2 which changes how container networks work? I am used to route containers through another container with VPN. I usually add --net=container:binhex-qbittorrentvpn to the extra parameters of the docker app i want to route through VPN. However this does not seem to work after upgrading...
May 12, 20251 yr Community Expert yes this still works...  review post:  3. Container (aka --network=container:<container_id_or_name>) -Shares network with another running container. -Use case: VPN containers (like Gluetun). -The secondary container inherits the network namespace of the VPN container. so setting:  --network=container:gluetun   This means: No port mappings in the template will be used. Only ports exposed by Gluetun can be used to reach the app. You cannot bind the same port twice across containers using the same network. -So even though a unraid template says: Container Port: 8000 Host Port: 8050 --That only works in Bridge mode. In --network=container:gluetun, the app must be accessed via the VPN container's IP/interface and exposed ports...    Edited May 12, 20251 yr by bmartino1 Data
May 12, 20251 yr Author Community Expert OK doesn't work for me. But then again my whole server went FUBAR once i upgraded to 7.1.2.
May 12, 20251 yr Community Expert what docker did you add to the --net=container:binhex-qbittorrentvpn  what posrt does it have... you should ba able to console into the docekr and run a curl or other ip check to see if its using the vpn... Â
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.