this post was submitted on 10 May 2026
78 points (100.0% liked)

Selfhosted

59049 readers
442 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

(First blog post ever, would appreciate your input!)

Edit: Title was a lil clickbaity

you are viewing a single comment's thread
view the rest of the comments
[–] Mikelius@lemmy.ml 2 points 14 hours ago (1 children)

I've just use iptables rules which default block all docker containers any network access. I assign static ranges to those I permit access, though. It does occasionally throw me off when adding new services and not understanding why sometimes they don't work right away, but I prefer it that way.

[–] Mubelotix@jlai.lu 1 points 12 hours ago

I totally agree and this is basically what it does except I added an allowlist feature, but I have some containers with an empty allowlist