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.

top 99 comments

sorted by: hot top controversial new old
[–] 37 points 9 months ago* (9 children)
  1. Because I'm old, crusty, and prefer software deployments in a similar manner.
  • source
  • hideshow 9 child comments
  • [–] [S] 11 points 9 months ago (4 children)

    I salute you and wish you the best in never having a dependency conflict.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 9 months ago (1 child)
  • 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.

  • source
  • parent
  • [–] 15 points 9 months ago (5 children)

    0, it's all organised nicely with nixos

  • source
  • hideshow 5 child comments
  • [–] [S] 7 points 9 months ago* (3 children)

    Boooo, you need some chaos in your life. :D

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 9 months ago (2 children)

    That's why I have one host called theBarrel and it's just 100 Chaos Monkeys and nothing else

  • source
  • parent
  • hideshow 2 child comments
  • [–] 14 points 9 months ago (11 children)

    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?

  • source
  • hideshow 11 child comments
  • [–] 7 points 9 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 9 months ago* (last edited 9 months ago) (3 children)

    A little of this, a little of that...I may also have a problem... >_>;

    The ListQuickstart

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

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 9 months ago (2 children)

    I look at this list and cry a little bit inside. I can't imagine having to maintain all of this as a hobby.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 9 months ago

    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.

  • source
  • parent
  • [–] 22 points 9 months ago* (4 children)

    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.

  • source
  • hideshow 4 child comments
  • [+] 9 points 9 months ago (3 children)
  • [–] 2 points 9 months ago

    I added the bookmarklet to my bookmarks bar so it's pretty easy to just navigate to the releases page on github and hit the button. I change the "visibility" setting to "show in its category" so things stay in their lanes rather than all go in a communal main feed but otherwise leave it as default.

    I did have to add some filters to the categories so it wouldn't flag all the -dev/-rc releases but that's it. The filters that work for me are:

    intitle:prototype-
    intitle:-build-number
    intitle:rc5
    intitle:rc6
    intitle:rc7
    intitle:rc8
    intitle:rc9
    intitle:-dev.
    intitle:Beta
    intitle:preview-
    intitle:rc1
    intitle:rc2
    intitle:rc3
    intitle:rc4
    intitle:"Release Candidate"
    intitle:Alpha
    intitle:-rc
    intitle:-alpha
    intitle:-beta
    intitle:develop-
    intitle:"Development release"
    intitle:Pre-Release
    
    
  • source
  • parent
  • [–] 9 points 9 months ago (2 children)

    Zero. Either it’s just a service with no wrappers, or a full VM.

  • source
  • hideshow 2 child comments
  • [–] 9 points 9 months ago (2 children)

    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.

  • source
  • hideshow 2 child comments
  • [–] [S] 6 points 9 months ago (1 child)

    I was watching a video yesterday where an org was churning 30K containers a day because they didn't profile their application correctly and scaled their containers based on a misunderstanding how Linux deals with CPU scheduling.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 9 months ago

    Yeah that shit is more common than people think.

    A big part of the business of cloud providers is that most orgs have no idea how to do shit. Their enterprise consultants are also wildly variable in competence.

    There was also a large amount of useless bullshit that I needed to cut down since being hired at my current spot, but the amount of containers is actually warranted. We do have that traffic, which is both happy and sad, since while business is booming, I have to deal with this.

  • source
  • parent
  • [–] 9 points 9 months ago (4 children)

    I am like Oprah yelling “you get a container, you get a container, Containers!!!” At my executables.

    I create aliases using toolbox so I can run most utils easily and securely.

  • source
  • hideshow 4 child comments
  • [–] 2 points 9 months ago* (last edited 9 months ago) (3 children)
  • [–] 3 points 9 months ago (2 children)

    Podman toolboxes, which layer a do gained over your user file system, allowing you to make toolbox specific changes to the system that only affect that toolbox. 

    I think it’s oringinally meant for development of desktop environments and OS features, but you can put most command line apps in them without much feauture breakage. 

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 9 months ago (1 child)

    I always saw them pitched by Fedora as the blessed way to run CLI applications on an immutable host.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 9 months ago

    That’s why I use them, but they are missing the in ramp to getting this working nicely for regular users. 

    E.g. how do I install neovim with toolbox and get Wayland clipboard working, without doing a bunch of manual work? It’s easy to add to my ostree, but that’s not really the way it should be. 

    I ended up making a bunch of scripts to manage this, but now I feel like I’m one step away from just using nixos. 

  • source
  • parent
  • [–] 8 points 9 months ago* (last edited 9 months ago) (6 children)

    Zero.

    About 35 NixOS VMs though, each running either a single service (e.g. Paperless) or a suite (Sonarr and so on plus NZBGet, VPN,...).

    There's additionally a couple of client VMs. All of those distribute over 3 Proxmox hosts accessing the same iSCSI target for VM storage.

    SSL and WireGuard are terminated at a physical firewall box running OpnSense, so with very few exceptions, the VMs do not handle any complicated network setup.

    A lot of those VMs have zero state, those that do have backup of just that state automated to the NAS (simply via rsync) and from there everything is backed up again through borg to an external storage box.

    In the stateless case, deploying a new VM is a single command; in the stateful case, same command, wait for it to come up, SSH in (keys are part of the VM images), run restore-<whatever>.

    On an average day, I spend 0 minutes managing the homelab.

  • source
  • hideshow 6 child comments
  • [–] 1 point 9 months ago (2 children)

    Why VMs instead of contsiners? Seems like way more processing overhead.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 9 months ago (1 child)

    Eh... Not really. Qemu does a really good job with VM virtualizarion.

    I believe I could easily build containers instead of VMs from the nix config, but I actually do like having a full VM: since it's running a full OS instead of an app, all the usual nix tooling just works on it.

    Also: In my day job, I actually have to deal quite a bit with containers (and kubernetes), and I just... don't like it.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 9 months ago

    Yeah, just wondered because containers just hook into the kernal in a way that doesn't have overhead. Where as a VM has to emulate the entire OS. But hey I get it, fixing stuff inside the container can be a pain

  • source
  • parent
  • [–] 6 points 9 months ago (1 child)

    Am not using docker yet. Currently I just have one Proxmox LXC, but am planning on selfhosting a lot more in the near future...

  • source
  • hideshow 1 child comment
  • [–] 5 points 9 months ago (4 children)

    59 according to docker info.

  • source
  • hideshow 4 child comments
  • [–] [S] 6 points 9 months ago (3 children)

    Hot damn. That is a far better way then counting the lines from docker ps

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 9 months ago

    How it started : 0

    Max : 0

    Now : 0

    Iso27002 and provenance validation goes brrrrr

  • source
  • [–] 5 points 9 months ago

    9 containers of which 1 is container manager with 8 containers inside (multi-containers counted as 1). And 9 that are installed off the NAS app store. 18 total.

  • source
  • [–] 5 points 9 months ago (11 children)

    I still haven't figured out containers. 🙁

  • source
  • hideshow 11 child comments
  • [–] 3 points 9 months ago (10 children)

    How come? What do you use to run them and what is it you have a hard time with?

  • source
  • parent
  • hideshow 10 child comments
  • [–] 2 points 9 months ago* (9 children)

    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.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 6 points 9 months ago (5 children)

    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.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 9 months ago (3 children)

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

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 9 months ago (2 children)

    Docker Compose is really the easiest way to self-host.

    Copy a file, usually provided by the developers of the app you want to run, change some values if instructed by the # comments, run docker compose up and it "just works".

    And I say that as someone who has done everything from distro-provided packages to compiling from source, Nix, podman systemd, and currently running a full-blown multi-node distributed storage Kubernetes cluster at home.

    Just use docker compose.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 9 months ago (2 children)

    I'm pretty sure I was at the same point years ago. The good thing is, next time you look into containers it'll likely be really easy and you'll wonder where you got stuck a year or two ago.

    At least that's what has happened to me more times than I can remember.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 9 months ago

    You were totally right. Got Navidrome set up last night, and just finished setting up Jellyfin. There were a few places I was scratching my head (the official documentation for both those isn't great if you don't already know how docker works) but I worked through it and now they're both up and running great! Appreciate the kind words!

  • source
  • parent
  • [–] 4 points 9 months ago* (last edited 9 months ago) (7 children)

    40 containers behind traefik, but I did just add a new sablier middleware to stop when iddle and start when first requested. Electricity is not cheap for me. But i got lucky to add 64GB RAM in my NAS and 128GB Ram in Desktop last march before prices went crazy

  • source
  • hideshow 7 child comments
  • [–] 1 point 9 months ago* (6 children)

    but I did just add a new sablier middleware to stop when iddle and start when first requested.

    Would you mind expounding on this? Electricity is fairly affordable in my locale, however I've been on a mission to cut out consumption when it's not needed. Have you noticed an ROI?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 9 months ago* (1 child)

    yes as most service sleep, and time to spin them up is fast. Moreover some services continuously poll folders and avoid disks to sleep. Letting disks sleep the whole night is a good idea if not in use, this won't shorten their lifespan.

    In here it is .30 pro Kwh

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 9 months ago (3 children)

    I wouldn't expect it to matter much, idle processes are pretty cheap.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 9 months ago* (1 child)

    yes and no...

    • Idle process are not cheap: some processes avoid all disks to sleep. .
    • In Europe electricity is not cheap, a bit more than .30 euro/kwh
  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 9 months ago

    What I've been doing is running a cron at a certain time in the evening, shutting down the server, and am working on a WOL sequence from my pfsense box fired by a cron, to crank it back up. Since it sits idle for 12 hours out of the 24, I just didn't see a need to keep it sucking up electricity.

    Of course, I'm not running any midnight, mass downloads of Linux iso's, and I have no other users save myself. If I had users, I'd pass the hat.

  • source
  • parent
  • [–] 4 points 9 months ago*

    At my house around 10-15. For lemmy.ca and our other sites, 35ish maybe. At work... hundreds.

  • source
  • [–] 4 points 9 months ago

    11 running on my little N150 box. Barely ever breaks a sweat.

  • source
  • [–] 4 points 9 months ago*

    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.

  • source
  • [–] 4 points 9 months ago

    I have 43 running, and this was a great reminder to do some cleanup. I can probably reduce my count by 5-10.

  • source
  • [–] 4 points 9 months ago

    I recently went from 0 to 1. Reinstalled my VPS under debian, and decided to run my forgejo instance with their rootless container. Mostly as a learning experience, but also to easily decouple the forgejo version from whichever version my distro packages.

  • source
  • [–] [B] 6 points 9 months ago* (last edited 9 months ago)

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

    Fewer Letters More Letters
    DNS Domain Name Service/System
    LXC Linux Containers
    NAS Network-Attached Storage
    Plex Brand of media server package
    SSH Secure Shell for remote terminal access
    SSL Secure Sockets Layer, for transparent encryption
    VPN Virtual Private Network
    VPS Virtual Private Server (opposed to shared hosting)
    k8s Kubernetes container management package

    9 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

    [Thread #42 for this comm, first seen 29th Jan 2026, 11:00] [FAQ] [Full list] [Contact] [Source code]

  • source
  • [–] 3 points 9 months ago

    36, with plans for more

  • source
  • [–] 3 points 9 months ago

    About 62 deployments with 115 "pods"

  • source
  • [–] 3 points 9 months ago

    51 containers on my Unraid server, but only 39 running right now

  • source
  • [–] 3 points 9 months ago

    two, one for running discord backup viewer webui and the other for archiveteam warrior containers

  • source
  • [–] 3 points 9 months ago

    Running home assistant with a few addons on a mostly dormant raspberry pi. This totals to 19 lines.

  • source
  • [–] 3 points 9 months ago (2 children)

    64 containers in total, 60 running - the remaining 4 are Watchtowers that I run manually whenever I feel like it (and have time to fix things if something should break).

  • source
  • hideshow 2 child comments
  • [–] 3 points 9 months ago

    I don't have access to my server right now, but it's around 20 containers on my little N100 box.

  • source
  • [–] 3 points 9 months ago

    35 containers and everything is running stable and most of it is automatically updated. In case something breaks I have daily backups of everything.

  • source
  • [–] 3 points 9 months ago

    26 tho this include multi container services like immich or paperless who have 4 each.

  • source
  • [–] 3 points 9 months ago

    I have currently got 23 on my n97 mini pc and 3 on my raspberry pi 4, making 26 in total.

    I have no issues managing these. I use docker compose for everything and have about 10 compose.yml files for the 23 containers.

  • source
  • [–] 3 points 9 months ago

    None, if it's not in a Debian repo I don't deploy it on my stable server.

    It's not really about docker itself, I just don't think software has married enough if it's not packaged properly

  • source
  • [–] 3 points 9 months ago

    There is a post about getting overwhelmed by 15

    I made the comment 'Just 15' in jest. It doesn't matter to me. Run 1, run 100. The comment was just poking the bear as it were. No harm nor foul intended. Sorry if it was received differently.

  • source
  • load more comments
    view more: next ›