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.
All of you bragging about 100+ containers, please may in inquire as to what the fuck that’s about? What are you doing with all of those?
A little of this, a little of that…I may also have a problem… >_>;
The List
Quickstart
Databases
Database Admin
Database Exporters
Networking Admin
Legally Acquired Media Display
Education
Books
Storage
Archival Storage
Backups
Monitoring
Metrics
Cameras
HomeAuto
Specific Tasks
Other
Plus a few more that I redacted.
I look at this list and cry a little bit inside. I can’t imagine having to maintain all of this as a hobby.
From a quick glance I can imagine many of those services don’t need much maintenance if any. E.g. RickRoll likely never needs any maintenance beyond the initial setup.
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.
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
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.
Ironic that Nextcloud AIO spins up multiple…
Not bragging. It is what it is. I run a plethora of things and that’s just on the production server. I probably have an additional 10 on the test server.
100 containers isn’t really a lot. Projects often use 2-3 containers. Thats only something like 30-50 services.
“Only”
Things and stuff. There is the web front end, API to the back end, the database, the redis cache, mqtt message queues.
And that is just for one of my web crawlers.
/S