-
6.8.3 use network from VPN Docker
I've been running a set of containers sharing their network as described here for a few days now, and I have had a few issues. Just wanted to post them here to see if you guys are getting the same problems: Using alturismo/ovpn_privoxy as my base container and vpn, the vpn seems to go down after a day or so. When I see everything is stopped - no vpn traffic - I restart the container and everything lights back up as expected. This could be the several things, but I feel like the VPN client is losing the connection and not reconnecting automatically. When I do have to restart the vpn, I can't just restart the main container. I have to restart every child container. That's a little tedious. The restarted child containers don't always start correctly, sometimes needing another restart. I seem to have better luck with this process: stop the children, restart the main container, start the children. But with eight-ish child containers, that's a real pain. Another challenge, that I haven't looked into yet, is that I need to allow traffic from my VPN container to a single IP on my normal LAN. My first thought is that maybe the route can be added in the OVPN files to have the VPN push the route to the network stack. If not, I don't know how else I might tackle this. Anyone else doing this?
-
6.8.3 use network from VPN Docker
Another thought I had was that I would like to be able to run some kind of browser through the VPN. Obviously, I could setup some kind of proxy and point my browser at it, but that's not ideal for my use case. I just want to be able to pop on to the VPN and check out some web sites. This is what I found: https://hub.docker.com/r/jlesage/firefox Firefox in a container. Very simple setup, good to go.
-
6.8.3 use network from VPN Docker
Yep, this worked great, and was extremely easy to setup. EDIT: This worked great until it didn't - the openvpn container would loose the connection after a few hours and had to be restarted. I switched to https://github.com/alturismo/ovpn_privoxy [Updated] 1. Added the ovpn_privoxy container downloaded the PIA ovpn file from here: https://www.privateinternetaccess.com/openvpn/openvpn.zip started the container once, then stopped changed login, password in the file, per the github instructions renamed all my ovpn files to use underscore rather than space - ovpn files with spaces seemed to fail I DID change my network from bridge to Custom:BR0 because I wanted my apps to use a specific IP added static IP to vpn container 2. Opened my existing containers and set network to NONE, and added extra param of '--net=container:pia' 3. Confirmed by opening container console and using 'curl https://ipinfo.io/ip' 4. Because I can't seem to get the docker admin page to open the webui, I added a container for DashMachine to serve as a landing page Couple of notes: 1. I could no longer get it to redirect ports. Example, I wanted DashMachine mapped to port 80, but it ignored my mapping and used the default 5000. 2. Docker admin page no longer shows 'WebUI' option on these containers. Even when I hard coded the IP and port. 3. If you do what I did and forget to change network to none, it will fail to load and take your container out of the list. Just add it back manually using the 'add container' button. All your setting will still be there. At least mine were.
-
6.8.3 use network from VPN Docker
I am working on a container stack using this one: https://github.com/ColinHebert/pia-openvpn Haven't gotten it all sorted yet, but I was able to connect with a test container and echo my IP. Returned the proper VPN IP, so I think it's going to be fine.