this post was submitted on 20 Sep 2024
26 points (93.3% liked)

Selfhosted

40329 readers
348 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I honestly can't get my head around this. I have a machine with Linux (endeavouros), and docker with a few containers. Since I want all the traffic from this system to go through the VPN, do I need to set up gluetun? I think not, but I am not 100% sure...

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 6 points 2 months ago (1 children)
[–] Polite_Crocodile@lemmy.dbzer0.com 5 points 2 months ago (3 children)

Ok, thanks. So if I'm getting this right every container should return the VPN IP with curl ifconfig.me

[–] azron@lemmy.ml 7 points 2 months ago

That's correct and a good way to test it out.

[–] pearsaltchocolatebar@discuss.online 4 points 2 months ago (1 children)

Yeah, when you have the VPN running all of your external traffic should go through it. It starts to get complicated when you only want a specific container/user to use/bypass the VPN.

Perfect, thanks!