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 register to comment.
I have 43 running, and this was a great reminder to do some cleanup. I can probably reduce my count by 5-10.
61 containers in 26 docker files.
49, I could imagine running all of those bare would be hard with dependencies
I don’t use them. I’m using OpenBSD on my server which don’t support this feature.
I know using work as an example is cheating, but around 1400-1500 to 5000-6000 depending on load throughout the day.
At home it’s 12.
- Because I’m old, crusty, and prefer software deployments in a similar manner.
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.
I salute you and wish you the best in never having a dependency conflict.
I’ve been resolving them since the late 90s, no worries.
Uh… Probably somewhere around 150?
None. I run my services they way they are meant to be run. There is no point in containers for a small setup. Its kinda lazy and you miss out on how to install them.
Small setups can very easily turn into large setups without you noticing.
The only bare-metal setup I’d trust to be scaleable is Nix flakes (which I’m actually very interested in migrating to at some point)
I’ve never even heard of NIX flakes before today. It looks like another soluion in search of a problem. I trust debian and I trust bare metal more than any container setup. I run multiple services on one machine. I currently have two machines to run all my services. No problems and no downtime other than a weekly update and reload. All crontabed, all automatic.
At work I have multiple services all running in KVM including some windows domain controllers. Also no problem and weekly full backups are a worry free. Only requiring me to checks them for consistency.
In short as much as people try to push containers they are only useful if you are dealing with more than few services. No home setup should be that large unless someong is hosting for others.
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.
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.
Ironic that Nextcloud AIO spins up multiple…
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.
I still haven’t figured out containers. 🙁
How come? What do you use to run them and what is it you have a hard time with?
I’m using docker. Tried to set up Jellyfin in one but I couldn’t for the life of me figure out how to get it to work, even following the official documentation. Ended up just running the jellyfin package from my distros repo, which worked fine for me. Also tried running a tor snowflake, which worked, but there was some issue with the NAS being restricted and I couldn’t figure out how to fix that. I kinda gave up at that point and saved the whole container thing to figure out another day. I only switched to Linux and started self-hosting last year, so I’m still pretty new to all of this.
If you do decide to look in to containers again and get stuck please make a post. We are glad to help out. A tip I can give you when asking for help. Tell the system you are using and how. Docker with compose files or portainer or something else etc. If using compose also add the yaml file you are using.
I will definitely try again at some point in the next year, so I will keep that in mind! I appreciate the kind words. A lot of what you said is over my head at the moment though, so I’ve got my work cut out for me. 😅
Zero. Either it’s just a service with no wrappers, or a full VM.
Why a full VM, that seems like a ton of overhead
140 running containers and 33 stopped (that I spin up sometimes for specific tasks or testing new things), so 173 total on Unraid. I have them gouped into:
- 118 Auto-updates (low chance of breaking updates or non-critical service that only I would notice if it breaks)
- 55 Manual-updates (either it’s family-facing e.g. Jellyfin, or it’s got a high chance of breaking updates, or it updates very infrequently so I want to know when that happens, or it’s something I want to keep particular note of or control over what time it updates e.g. Jellyfin when nobody’s in the middle of watching something)
I subscribe to all their github release pages via FreshRSS and have them grouped into the Auto/Manual categories. Auto takes care of itself and I skim those release notes just to keep aware of any surprises. Manual usually has 1-5 releases each day so I spend 5-20 minutes reading those release notes a bit more closely and updating them as a group, or holding off until I have more bandwidth for troubleshooting if it looks like an involved update.
Since I put anything that might cause me grief if it breaks in the manual group, I can also just not pay attention to the system for a few days and everything keeps humming along. I just end up with a slightly longer manual update list when I come back to it.
I’ve never looked into adding GitHub releases to FreshRSS. Any tips for getting that set up? Is it pretty straight forward?
Am not using docker yet. Currently I just have one Proxmox LXC, but am planning on selfhosting a lot more in the near future…
Awesome! I like ProxMox. Check out the Helper Scripts if you haven’t already. Some people like them, some don’t.
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 else
