Selfhosted

43945 readers

444 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Is this safe to use? (leminal.space)

submitted 1 week ago by Flamangoman@leminal.space to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

Hi all,

I've been going through a guide by techhut for setting up gluetun, and there's a small bit of code that he adds in from his github, and I want to understand the implications of using it.

He writes:

When containers are in the same docker compose all you need to add is a network_mode: service:container_name and open the ports through the gluetun container. See example from the compose.yaml below.

And here's the code: services: gluetun: # This config is for wireguard only tested with AirVPN image: qmcgaw/gluetun container_name: gluetun ... ports: - 8888:8112 # deluge web interface - 58846:58846 # deluge RPC deluge: image: linuxserver/deluge:latest container_name: deluge ... network_mode: service:gluetun

If you could please explain to me what this means, and if there are any risks associated with this, I would really appreciate it.

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

[–] Evkob@lemmy.ca 6 points 1 week ago (1 children)

Any ports used in docker will be open on your computer and accessible to any device in your network.

However, to open up a port to the internet, you'd have to do port-forwarding on your router. If you haven't done that, any incoming connections will just be dropped at the router-level.

[–] catloaf@lemm.ee 6 points 1 week ago (1 children)

Assuming they use NAT. Almost certainly true for IPv4, very unlikely for IPv6. And you should have a firewall too.

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 week ago

Exactly. I have my firewall set up to block everything I don't explicitly allow through. That way if I'm a little loose with running things on ports, it at least won't leak ports past the firewall.