Selfhosted

60542 readers

552 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the link in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post. )

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

Secure Way to Expose Docker Containers to the Internet? (lemmy.one)

submitted 1 year ago by MoonlitSanguine@lemmy.one to c/selfhosted@lemmy.world

43 comments fedilink hide all child comments

I've been researching different ways to expose Docker containers to the internet. I have three services I want to expose: Jellyfin, Omnivore (Read-it-later app), and Overseerr.

I've come across lots of suggestions, like using Nginx with Cloudflared, but some people mention that streaming media goes against Cloudflared tunnel TOS, and instead recommend Tailscale, or Traefik, or setting up a WireGuard VPN, or using Nginx with a WireGuard VPN.

The amount of conflicting advice has left me confused. So, what would be the best approach to securely expose these containers?

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

[–] plm00@lemmy.ml 18 points 1 year ago (1 children)

"Secure" and "exposed" are antonyms in this scenario, that's the nature of the beast. I use Nginx which I have a domain pointing to. Worst case scenario, a hacker brute forces access to my container and mucks around within the confines. As I understand from a WireGuard VPN, there's an added level of security. You have to use the VPN to get access to your home ports, and then you can access your Docker containers as configured. There's an added layer of security.

Some things to consider:

Do you have a target on your back?
Does your container contain sensitive data?
If so, does your container have access to external directories?
Does your project have security options like Geo Blocking, rate limiting, etc?

I've been running some local servers for a few years only behind Nginx. So far nothing bad has happened. But that doesn't mean something bad couldn't happen later.

[–] MoonlitSanguine@lemmy.one 1 points 1 year ago (1 children)

Thanks for the info.

Do you have a target on your back?

No.

Does your container contain sensitive data?

No.

If so, does your container have access to external directories?

I have a hard drive mounted to the media folder that Jellyfin can access, and also a config folder. Omnivore/Overseer will probably be similar once I add them. Could this be a problem?

  - '/home/${USER}/server/configs/jellyfin:/config'
  - '/home/${USER}/server/media:/data/media'

Does your project have security options like Geo Blocking, rate limiting, etc?

That is a good idea. Thankyou

[–] plm00@lemmy.ml 2 points 1 year ago

What I was referring to is called a Bind Mount, where host directories are exposed to the docker container. You may be fine if it's an external hard drive. I use bind mounts because they're easier to back up, but I acknowledge they are less safe.

You may be perfectly fine as you are now. My (and others) suggestions are for added security. As it stands, if there's no target on your bind, the only bad traffic you'll get are from bots trying to pick away at your domain and sub domains. Generally they're not a problem. But being extra safe costs nothing but time.