this post was submitted on 19 Dec 2024
35 points (85.7% liked)

Selfhosted

40677 readers
337 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Yo,

Wandering what the limit is when it comes to how many containers I can run. Currently I'm running around 15 containers. What happens if this is increased to say, 40? Also, can docker containers go "idle" when not being used - to save system resources?

I'm running a i7-6700k Intel cpu. Doesn't seem to be struggling at all with my current setup at least, maybe only when transcoding for Jellyfin.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 34 points 2 days ago (1 children)

A Docker container is essentially a process running on your machine. Just like any other process. It can be idle, stopped or hogging the CPU. You can use Docker constraints to limit resource use if you want to, memory, CPU and network to name a few.

So, can you run 40 processes?

Very likely. Probably 400 or 4000, depending on CPU usage and memory.

I ran that particular CPU with 64 GB of RAM and used it to run multiple virtual machines, my main debian desktop and a VM specifically as a docker host, running dozens of instances of Google Chrome without ever noticing it slowing down.

Then the power cable shortened out and life was never the same. That was six months ago, the machine was a late 2015 iMac running macos and VMware Fusion.

[–] Voroxpete 14 points 2 days ago (1 children)

I'll add here that the "docker top" command allows you to easily see what kind of resources your containers are using.

If you prefer a UI, Dozzle runs as a container, is super lightweight, requires basically no setup, and makes it very easy to see your docker resource usage.

[–] [email protected] 3 points 2 days ago (1 children)
[–] [email protected] 2 points 1 day ago (1 children)

Also try Lazydocker, I think it's far superior to Dozzle for features. If you run it in a folder with a docker-compose.yml, it'll just show the processes from that set of containers, if you run it in any other folder it'll show all your docker containers.

[–] [email protected] 1 points 1 day ago

This i will definitely look into, love dozzle for when I need to troubleshoot.