--- title: I capped CPU and RAM on my Docker containers, and my... description: A homelab operator running a bare-metal Debian server with 20+ Docker containers on modest hardware (i5-6300U, 12GB RAM) describes fixing intermittent... canonical: https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: I capped CPU and RAM on my Docker containers, and my entire self-hosted homelab became reliable | daily.dev og:description: A homelab operator running a bare-metal Debian server with 20+ Docker containers on modest hardware (i5-6300U, 12GB RAM) describes fixing intermittent... og:url: https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw og:image: https://api.daily.dev/og/posts/anE2MItyw.png og:image:alt: I capped CPU and RAM on my Docker containers, and my entire self-hosted homelab became reliable og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # I capped CPU and RAM on my Docker containers, and my entire self-hosted homelab became reliable **[XDA Developers](https://daily.dev/sources/xda-developers)** · 4 min read · 4 upvotes · 0 comments ## Summary A homelab operator running a bare-metal Debian server with 20+ Docker containers on modest hardware (i5-6300U, 12GB RAM) describes fixing intermittent sluggishness by setting explicit CPU and RAM limits on individual containers. Without limits, containers could freely expand into shared headroom, causing services like Jellyfin transcoding to disrupt others. Using Beszel to review a week of usage data, the author selectively capped resource-hungry containers while leaving critical services like Postgres and Portainer unlimited to avoid OOM kills during writes. The result was a more predictable, 'boring' resource graph rather than dramatic performance gains, with the trade-off being slower completion times for capped workloads under peak load. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What happens when a Docker container hits its memory limit versus its CPU limit? A container that reaches its memory ceiling gets OOM-killed by the kernel, while a container that hits its CPU limit is throttled by the scheduler rather than killed. This difference matters when deciding which services are safe to cap: memory limits carry a hard failure risk, so critical stateful services like databases are often better left unrestricted. _Anyone tuning container resource limits can track homelab and Docker practices on daily.dev._ ### Should I set Docker resource limits on database containers like Postgres in my homelab? Generally no, because limiting memory on a database service risks application failure, potentially during a write operation, if it gets OOM-killed. A safer approach is to leave critical services like Postgres and Portainer unrestricted while capping CPU and RAM on less critical, load-spiking containers such as media transcoders or ML services. _Homelab operators weighing which services to cap can follow more self-hosting reliability tips on daily.dev._ ## Similar posts on daily.dev - [I stopped running every Docker container 24/7, and my home server has never been better](https://daily.dev/posts/i-stopped-running-every-docker-container-24-7-and-my-home-server-has-never-been-better-ofekwwi4g) · XDA Developers · 0 upvotes · 0 comments - [I thought my home lab needed more hardware – it actually needed fewer services](https://daily.dev/posts/i-thought-my-home-lab-needed-more-hardware-it-actually-needed-fewer-services-fr9jcd11j) · XDA Developers · 0 upvotes · 0 comments - [I kept waiting for Docker to fail, but nineteen containers on bare metal proved Proxmox wrong](https://daily.dev/posts/i-kept-waiting-for-docker-to-fail-but-nineteen-containers-on-bare-metal-proved-proxmox-wrong-d2fhasfts) · XDA Developers · 1 upvotes · 1 comments - [Linux containers do what my Proxmox VMs couldn't: run a dozen services without wasting half my memory](https://daily.dev/posts/linux-containers-do-what-my-proxmox-vms-couldn-t-run-a-dozen-services-without-wasting-half-my-memor-4f3lykuas) · XDA Developers · 2 upvotes · 1 comments - [Windows 11's system requirements killed my old laptop — so I made it a home server instead](https://daily.dev/posts/windows-11-s-system-requirements-killed-my-old-laptop-so-i-made-it-a-home-server-instead-9ume2nd1v) · XDA Developers · 2 upvotes · 0 comments --- Tags: [#linux](https://daily.dev/tags/linux), [#docker](https://daily.dev/tags/docker), [#self-hosting](https://daily.dev/tags/self-hosting), [#homelab](https://daily.dev/tags/homelab) [View this post on daily.dev](https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"I capped CPU and RAM on my Docker containers, and my entire self-hosted homelab became reliable","url":"https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw"},"datePublished":"2026-08-31T17:03:52.807Z","dateModified":"2026-08-31T17:16:46.368Z","description":"A homelab operator running a bare-metal Debian server with 20+ Docker containers on modest hardware (i5-6300U, 12GB RAM) describes fixing intermittent...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/871a296dc6043b9d4f089fbe43419b47?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/871a296dc6043b9d4f089fbe43419b47?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"XDA Developers","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"XDA Developers","logo":"https://media.daily.dev/image/upload/s--kCg6yyAP--/f_auto,q_auto/v1774964407/logos/xda-developers?_a=BAMAMiWQ0","url":"https://daily.dev/sources/xda-developers"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux,docker,self-hosting,homelab","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"XDA Developers","item":"https://daily.dev/sources/xda-developers"},{"@type":"ListItem","position":3,"name":"I capped CPU and RAM on my Docker containers, and my entire self-hosted homelab became reliable"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/i-capped-cpu-and-ram-on-my-docker-containers-and-my-entire-self-hosted-homelab-became-reliable-ane2mityw#faq","mainEntity":[{"@type":"Question","name":"What happens when a Docker container hits its memory limit versus its CPU limit?","acceptedAnswer":{"@type":"Answer","text":"A container that reaches its memory ceiling gets OOM-killed by the kernel, while a container that hits its CPU limit is throttled by the scheduler rather than killed. This difference matters when deciding which services are safe to cap: memory limits carry a hard failure risk, so critical stateful services like databases are often better left unrestricted. Anyone tuning container resource limits can track homelab and Docker practices on daily.dev."}},{"@type":"Question","name":"Should I set Docker resource limits on database containers like Postgres in my homelab?","acceptedAnswer":{"@type":"Answer","text":"Generally no, because limiting memory on a database service risks application failure, potentially during a write operation, if it gets OOM-killed. A safer approach is to leave critical services like Postgres and Portainer unrestricted while capping CPU and RAM on less critical, load-spiking containers such as media transcoders or ML services. Homelab operators weighing which services to cap can follow more self-hosting reliability tips on daily.dev."}}]} ```