proxmox
Deploy and Manage a VPN for your Docker Containers via Dockge!
Deploy and Manage a VPN for your Docker Containers via Dockge!
#Deploy #Manage #VPN #Docker #Containers #Dockge
“DB Tech”
In this video we’re going to take a look at how to run the traffic of Docker containers through a VPN container for better online security and anonymity.
Thanks to YouTube viewer Red Rabbit for leaving a comment asking me to make a video showing how to run the traffic of different Docker…
source
To see the full content, share this page by clicking one of the buttons below |
How does this work when you have 2 or more services on the same internal port? Let's say you have 2 services on 80:80 and you normally identify as 80:80 and 81:80. How would gluetun route this traffic? Or would the container even build because you're mapping 2 different external ports to the same internal port?
Thanks!
Nice tutorial! Question, when wanting to run a stack through a Gluetun container, do you have to add
network_mode: container:gluetun
networks:
gluetun_default:
external: true
To all the apps (one by one) within the stack, or is there a more general way to do that? do you know?
With Gluetun – If vpn connection down does it route traffic over our IP or fail?
I know others needed to create firewall rules.
Hope your feeling well
Waiting for a gluetun free version…😂
Great video as always buddy, random question if I need to access a port on a remote machine but don't want to use a VPN. What other options do I have? I tired Googleing but I only get VPN options.
I've been using Gluetun for a few months and it has worked out pretty nicely. The only time I have any issues is if one of the docker services that wants to use the Gluetun VPN finishes starting up before Gluetun is done starting up it can cause an issue sometimes. But I have only experienced that with one of my docker apps and it doesn't happen all of the time.
as usual great vid and explanation. I'd like to see a vid on ampache. thank you
Excellent video well broken down thank you
Can the "Stop & Inactive" activity be replaced by "docker stop <container_name> && docker rm <container_name>" in ssh?
I was wondering if there is a way to assign a "static" identifier to gluetun container in order to avoid to re-deploy every single container every time you add a new one.
I don't understand the use for /dev/tun/net device forwarding, what does it do? Why is it needed at all? I don't have that line in my docker-compose.yml and it works fine 🤔
Is it maybe only needed when you are deploying other services with other docker-compose files, like you are doing? I guess it would make sense if something else on the host needs to tunnel? Is that it?
I deploy my entire stack in one docker-compose (gluetun and all the services I run through it)