Saw the release notes adding this support to 6.8.3.  Anyone know how to engage this?

Just wanted to add a "me too". I am looking to send specific docker containers through a wireguard (plugin/or/docker) client but leave everything else as normal

I'm interested in this feature and I think I see how it works. I have a VPN container (named piavpn) and a qBittorrent container that uses the VPN container network stack.  I achieve this by setting the container network to "none" and then in the extra parameters field, I have 

--net=container:piavpn

In the past, if I would upgrade my VPN container, the download container would cease to work as the container had bound itself to the previous "piavpn" container by the hex Container ID, not by name. I would have to delete and recreate my downloader container, which would also fail because there were two conflicting --net options (i.e. --net=none and --net=container:piavpn). I would previously copy the container create command, remove the --net=none argument, and then rerun the resulting command on the unraid console.

With this new feature, things seem to work seamlessly.  When I upgraded my VPN container, Unraid recognized the dependency my downloader container had, briefly had a status of "Repairing" , and continued to work.  Similarly, when upgrade the downloader, Unraid seems to resolve the conflicting --net arguments on its own, preferring the one I had set in Extra Parameters.

Thanks Unraid devs!

1 minute ago, tankertux said:

I'm interested in this feature and I think I see how it works. I have a VPN container (named piavpn) and a qBittorrent container that uses the VPN container network stack.  I achieve this by setting the container network to "none" and then in the extra parameters field, I have 

--net=container:piavpn

In the past, if I would upgrade my VPN container, the download container would cease to work as the container had bound itself to the previous "piavpn" container by the hex Container ID, not by name. I would have to delete and recreate my downloader container, which would also fail because there were two conflicting --net options (i.e. --net=none and --net=container:piavpn). I would previously copy the container create command, remove the --net=none argument, and then rerun the resulting command on the unraid console.

With this new feature, things seem to work seamlessly.  When I upgraded my VPN container, Unraid recognized the dependency my downloader container had, briefly had a status of "Repairing" , and continued to work.  Similarly, when upgrade the downloader, Unraid seems to resolve the conflicting --net arguments on its own, preferring the one I had set in Extra Parameters.

Thanks Unraid devs!

How did you setup your pia vpn docker. I have one setup but when i connect my other docker to my piavpn docker it can not connect. I have all the correct ports set on pia vpn docker too. Maybe a screenshot of how your pia docker is setup.

 

This is one Im trying to use. 

 

I said all that to say this...what pia docker are you using?

I am using qmcgaw/private-internet-access on a user defined network I named pianet

 

My settings: 

 

Advanced setting that is important:

 

 

Downloader uses the --net=container:piavpn option, and then I use Nginx to route a host port into the downloader web GUI.

 

Nginx Basic config:

 

Nginx Advanced View parameters:

 

Nginx.conf:

I'm looking at installing openvpn client but only force 1 docker to use it (example torrents) without applying the VPN on my whole network. Possible?

 

I did have it on my pfsense router, but it would severely impact my downloads throughout my entire network.