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.

  • StrawberryPigtails@lemmy.sdf.orgEnglish
    7·
    2 days ago

    In my case, most things that I didn’t explicitly make public are running on Tailscale using their own Tailscale containers.

    Doing it this way each one gets their own address and I don’t have to worry about port numbers. I can just type http://cars/ (Yes, I know. Not secure. Not worried about it) and get to my LubeLogger instance. But it also means I have 20ish copies of just the Tailscale container running.

    On top of that, many services, like Nextcloud, are broken up into multiple containers. I think Nextcloud-aio alone has something like 5 or 6 containers it spins up, in addition to the master container. Tends to inflate the container numbers.

    • GraveyardOrbit@lemmy.zipEnglish
      1·
      1 day ago

      Would tailscale services work as an alternative to this? My understanding is that you can ignore the load balancing and just proxy a name to a container port

      • StrawberryPigtails@lemmy.sdf.orgEnglish
        1·
        17 hours 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.