150
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 31 Jul 2023
150 points (97.5% liked)
Selfhosted
40359 readers
213 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Couldn't understand if it's a client in the sense other docker containers can use it, or what. Could somebody please clarify?
It's a docker container that runs an OpenVPN/Wireguard client in order to provide a connection for other containers, yes.
But you can just do that with a regular Wireguard container. Does this one do anything special? I haven't looked into it yet but I guess it's pre-configured for some providers?
It's a vpn client on steroids that creates a VPN network (based on your provider) which you can then use to run docker containers inside of, as well as create http & shadowsocks proxies for your VPN network etc.
To build on this since I have this setup now, it basically creates a new docker network that you can attach containers to, and have all of their traffic routed through it. Basically I have the gluetun container running, then in my qbittorrent docked-compose I have
network_mode: "container:gluetun".One thing to watch out for is you have to specify the ports in the gluetun docked-compose instead of in each docked-compose.
Additionally, if gluetun shuts down and the apps using it don't, you'll have to restart the apps using it. Not an issue if it's all in the same docker-compose file, but I like separating docker-compose services so I have qbittorrent/docker-compose.yml and gluetun/docker-compose.yml