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 must log in or # to comment.
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?
Kube makes it easy to have a lot, as a lot of things you need to deploy on every node just deploy on every node. As odd as it sounds, the number of containers provides redundancy that makes the hobby easy. If a Zimaboard dies or messes up, I just nuke it, and I don’t care whats on it.
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
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
Ironic that Nextcloud AIO spins up multiple…
100 containers isn’t really a lot. Projects often use 2-3 containers. Thats only something like 30-50 services.
A little of this, a little of that…I may also have a problem… >_>;
The List
Quickstart
- dockersocket
- ddns-updater
- duckdns
- swag
- omada-controller
- netdata
- vaultwarden
- GluetunVPN
- crowdsec
Databases
- postgresql14
- postgresql16
- postgresql17
- Influxdb
- redis
- Valkey
- mariadb
- nextcloud
- Ntfy
- PostgreSQL_Immich
- postgresql17-postgis
- victoria-metrics
- prometheus
- MySQL
- meilisearch
Database Admin
- pgadmin4
- adminer
- Chronograf
- RedisInsight
- mongo-express
- WhoDB
- dbgate
- ChartDB
- CloudBeaver
Database Exporters
- prometheus-qbittorrent-exporter
- prometheus-immich-exporter
- prometheus-postgres-exporter
- Scraparr
Networking Admin
- heimdall
- Dozzle
- Glances
- it-tools
- OpenSpeedTest-HTML5
- Docker-WebUI
- web-check
- networking-toolbox
Legally Acquired Media Display
- plex
- jellyfin
- tautulli
- Jellystat
- ErsatzTV
- posterr
- jellyplex-watched
- jfa-go
- medialytics
- PlexAniSync
- Ampcast
- freshrss
- Jellyfin-Newsletter
- Movie-Roulette
Education
- binhex-qbittorrentvpn
- flaresolverr
- binhex-prowlarr
- sonarr
- radarr
- jellyseerr
- bazarr
- qbit_manage
- autobrr
- cleanuparr
- unpackerr
- binhex-bitmagnet
- omegabrr
Books
- BookLore
- calibre
- Storyteller
Storage
- LubeLogger
- immich
- Manyfold
- Firefly-III
- Firefly-III-Data-Importer
- OpenProject
- Grocy
Archival Storage
- Forgejo
- docmost
- wikijs
- ArchiveTeam-Warrior
- archivebox
- ipfs-kubo
- kiwix-serve
- Linkwarden
Backups
- Duplicacy
- pgbackweb
- db-backup
- bitwarden-export
- UnraidConfigGuardian
- Thunderbird
- Open-Archiver
- mail-archiver
- luckyBackup
Monitoring
- healthchecks
- UptimeKuma
- smokeping
- beszel-agent
- beszel
Metrics
- Unraid-API
- HDDTemp
- telegraf
- Varken
- nut-influxdb-exporter
- DiskSpeed
- scrutiny
- Grafana
- SpeedFlux
Cameras
- amcrest2mqtt
- frigate
- double-take
- shinobipro
HomeAuto
- wyoming-piper
- wyoming-whisper
- apprise-api
- photon
- Dawarich
- Dawarich—Sidekiq
Specific Tasks
- QDirStat
- alternatrr
- gaps
- binhex-krusader
- wrapperr
Other
- Dockwatch
- Foundry
- RickRoll
- Hypermind
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.
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.
At my house around 10-15. For lemmy.ca and our other sites, 35ish maybe. At work… hundreds.
Server 1: 5 containers Server 2: 4 containers Server 3: 4 containers Server 4: 61 containers
Basically if a container is a resource hog, it gets moved somewhere with more resources or specialized hardware.
That’s a wee bit imbalanced. Is server 4 your big boi?
It’s the oldest, but not the most powerful. Not everything I host sees a lot of activity. But things like Plex/Jellyfin/Immich found their own hardware with better GPU support, and serious A/V or disk intense processes have a full spec PC available. There is also a remote backup system in place so a couple containers are duplicates.
44 containers and my average load over 15 min is still 0,41 on an old Intel nuc.
51 containers on my Unraid server, but only 39 running right now
0, it’s all organised nicely with nixos
Boooo, you need some chaos in your life. :D
That’s why I have one host called
theBarreland it’s just 100 Chaos Monkeys and nothing elseThis is the way.
I have 1 podman container on NixOS because some obscure software has a packaging problem with ffmpeg and the NixOS maintainers removed it.
docker: command not found
11 running on my little N150 box. Barely ever breaks a sweat.
$ docker ps | wc -l 14Just running 13 myself.
25, with your “docker ps” command, on my aging Nuc10 PC. Only using 5GB of its 16GB of RAM.
What, me worry?
Between 100 and 150.
@slazer2au Application containers: 30-40
System containers (including kube, Istio, CNI, etc): ~20Shifting from Istio sidecar mode to Istio ambient mode made a big difference.
I don’t have access to my server right now, but it’s around 20 containers on my little N100 box.
- Because I’m old, crusty, and prefer software deployments in a similar manner.
Agreed. Im tired after work. Debian/yunohost is good enough.
At work its hundreds of docker containers but all ci/cd takes care of that.
I salute you and wish you the best in never having a dependency conflict.
I’ve been resolving with them since the late 90s, no worries.
My worst dependency conflict was a libcurlssl error when trying to build on a precompiled base docker image.
I use Debian
Isn’t that harder?
It depends a lot on what you want to do and a little on what you’re used to. It’s some configuration overhead so it may not be worth the extra hassle if you’re only running a few services (and they don’t have dependency conflicts). IME once you pass a certain complexity level it becomes easier to run new services in containers, but if you’re not sure how they’d benefit your setup, you’re probably fine to not worry about it until it becomes a clear need.
Well the containers are grouped into services. I would easily have 15 services running, some run a separate postgres or redis while others do an internal sqlite so hard to say (I’m not where I can look rn).
If we’re counting containers then between Nextcloud and Home Assistant I’m probably over 20 already lol.
53
