(posting here because even though my issue is with a few specific containers, it seems to be a deeper underlying issues)

 

Here is an interesting one for you...

 

I have been using binhex-sabnzbd for a few days now and noticed it stopped working. After some sleuthing, it could not do DNS lookups even though other dockers could and /etc/resolv.conf was set perfectly (could ping 8.8.8.8 no problem but did not ping www.google.com).

 

When I change a variable (i.e. the VPN_REMOTE) it does not edit the file in the container. After looking around some other dockers, I saw that binhex-rtorrentvpn would not pass changes either...

 

If I delete the openvpn.ovpn file; the docker would not recreate it (using PIA)

 

I have already tried a new docker.img file, as well as destroying and recreating the container. Permissions are 0777 nobody:users. The regular binhex-sabnzbd works fine.

 

I am guessing its a R/W issue, but as of now I am stumped...

Strange, not quite sure what that may be. Sounds like it works with the regular (without VPN) version of the docker. If so I'd suggest trying this alternative approach that's worked very well for me over the years.

 

Instead of VPN at the Docker level, just use regular dockers and let them do what they do. Use a UnRaid plug-in, such as peter_sm's  OpenVPN Client and this tunnel everything through the VPN as default. To white-list a Docker or VM that you don't want to go through the VPN tunnel, they'll need an IP assigned to them on br0. Assign them an IP address on the br0, and add a static route from that IP to your Gateway in the network settings. I don't recommend doing that with a Docker for security reasons.

 

 

 

 

The OpenVPN client isn't designed to be used with something like PIA.  It's more to connect to an OpenVPN server.

 

I think there are security ramifications to using it to connect to a VPN service like PIA.

I figured it out.

 

Short version: Format change.

 

My containers were not passing variables because, there was nothing to receive them. There was a format change in the docker. Why I couldn't tell you, but I am sure the answer lies in the specific docker threads :-)

 

Everything back to normal