this post was submitted on 29 Jan 2026
118 points (97.6% liked)

Selfhosted

60210 readers
944 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

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

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.

But now I am curious, what are your counts? I would guess those of you running k*s would win out by pod scaling

docker ps | wc -l

For those wanting a quick count.

you are viewing a single comment's thread
view the rest of the comments
[–] StrawberryPigtails@lemmy.sdf.org 1 points 4 months ago

Possibly. I don't remember that being an option when I was setting things up last time.

From what I'm reading it's sounding like it's just acting as a slightly simplified DNS server/reverse proxy for individual services on the tailnet. Sounds Interesting. I'm not sure it's something I'd want to use on the backend (what happens if Tailscale goes down? Does that DNS go down too?), but for family members I've set up on the tailnet, it sounds like an interesting option.

Much as I like Tailscale, it seems like using this may introduce a few too many failure points that rely on a single provider. Especially one that isn't charging me anything for what they provide.