two, one for running discord backup viewer webui and the other for archiveteam warrior containers
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
36, with plans for more
Uh.. Probably somewhere around 150?
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.
12 LXCs and 2 VMs on proxmox. Big fan of managing all the backups with the web ui (It's very easy to back to my NAS) and the helper scripts are pretty nice too. Nothing on docker right now, although i used to have a couple in a portainer LXC.
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
I don't have access to my server right now, but it's around 20 containers on my little N100 box.

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).
13 with podman on openSUSE MicroOS.
i used to have a few more but wasn't using them enough so i cut them.
26 tho this include multi container services like immich or paperless who have 4 each.
35 containers and everything is running stable and most of it is automatically updated. In case something breaks I have daily backups of everything.
Running home assistant with a few addons on a mostly dormant raspberry pi. This totals to 19 lines.
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.
58, my cpu is usually around 10-20% usage. I really don’t have any trouble managing/maintaining these. Things break almost weekly but I understand how to fix them every time, it only takes a few minutes
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.
$ docker ps | wc -l
14
Just running 13 myself.
Between 100 and 150.
53
25, with your "docker ps" command, on my aging Nuc10 PC. Only using 5GB of its 16GB of RAM.
What, me worry?
@slazer2au Application containers: 30-40
System containers (including kube, Istio, CNI, etc): ~20
Shifting from Istio sidecar mode to Istio ambient mode made a big difference.
89 - 79 on my main server and 10 on my sandbox.
Server01: 64 Server02: 19 Plus a bunch of sidecar containers solely for configs that aren't running.
9
13 running on my little Synology.
Actually more than I expected, I would have guesses closer to 8
About 50 on a k8s cluster, then 12 more on a proxmox vm running debian and about 20 ish on some Hetzner auction servers.
About 80 in total, but lots more at work:)
- There are usually one or two of those that are just experimental and might get trashed.
My kubernetes cluster is sitting happily at 240, and technically those are pods some of which have up to 3 or 4 containers, so who knows the full number.
35 stacks 135 images 71 containers
74 across 2 proxmox nodes in a few lxcs