this post was submitted on 05 Mar 2025
17 points (90.5% liked)

Selfhosted

43945 readers
338 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
17
Is this safe to use? (leminal.space)
submitted 6 days 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
[–] sugar_in_your_tea@sh.itjust.works 22 points 6 days ago* (last edited 6 days ago) (5 children)

It's fine, it just grabs the network settings from the gluetun service.

Btw, your post is hard to read due to formatting. Surround the code block with triple backticks at the top and bottom like this:

```
code goes here
```

Example:

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
[–] Flamangoman@leminal.space 4 points 6 days ago (2 children)

Thank you so much for your reply. Follow up question, does this open up any ports to the greater internet in any way? That is really where my concern is, as I have heard that is dangerous to do

[–] Evkob@lemmy.ca 6 points 6 days 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 6 days 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 6 days 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.

[–] IronKrill@lemmy.ca 5 points 6 days ago* (last edited 6 days ago)

I'm using Gluetun via Docker Compose as well right now and can happily say all the ports exposed via the ports: setting are local network only. I could port forward them via the router probably (haven't tried) but I only use them for access via LAN. To expose ports over the VPN connection you use the FIREWALL_VPN_INPUT_PORTS environment variable. A stripped version of my current compose (example port numbers, not real) with LAN access to 6000 and WAN access to 1234 and 5678:

services:
  gluetun:
    image: qmcgaw/gluetun:latest
    restart: unless-stopped
    container_name: gluetun
    cap_add:
      - NET_ADMIN # in the default compose file i dunno what this does tbh
    environment:
      - VPN_SERVICE_PROVIDER=custom
      - VPN_TYPE=openvpn
      - OPENVPN_VERSION=<redacted>
      - OPENVPN_USER=<redacted>
      - OPENVPN_PASSWORD=<redacted>
      - OPENVPN_CUSTOM_CONFIG=/gluetun/custom.ovpn
      - FIREWALL_VPN_INPUT_PORTS=1234,5678 # allows ports through VPN connection
      - FIREWALL_OUTBOUND_SUBNETS=192.168.0.0/24 # I found that I needed this for certain LAN access
    ports:
      - 6000:6000 # port i access via LAN
    volumes:
      - /mnt/example/config.ovpn:/gluetun/custom.ovpn
load more comments (2 replies)