Selfhosted

59923 readers

761 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

128

gluetun: VPN client in a thin Docker container for multiple VPN providers (github.com)

submitted 2 years ago by anzo@programming.dev to c/selfhosted@lemmy.world

31 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] somebodyknows@lemmy.world 6 points 2 years ago (2 children)

Couldn't understand if it's a client in the sense other docker containers can use it, or what. Could somebody please clarify?

[–] bear@slrpnk.net 9 points 2 years ago* (last edited 2 years ago) (1 children)

It's a docker container that runs an OpenVPN/Wireguard client in order to provide a connection for other containers, yes.

[–] dan@upvote.au 3 points 2 years ago

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?

[–] gobbling871@lemmy.world 5 points 2 years ago* (last edited 2 years ago) (1 children)

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.

[–] finestnothing@lemmy.world 5 points 2 years ago

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