Docker and VMs on a NAS: What CPU Class You Actually Need
A NAS's self-hosting capability is set by CPU class and RAM, not marketing. The thresholds: ARM entry boxes handle file serving plus a couple of light containers, no VMs. Celeron/N100-class x86 (QNAP TS-x64, TerraMaster F4-424, Asustor AS5404T, UGREEN NASync, Synology DS224+) is the Docker sweet spot — Pi-hole, Home Assistant, a *arr stack, and Vaultwarden-class services run comfortably, and one light VM is feasible if you upgrade the RAM. Ryzen/Core-class boxes (Synology DS923+ band and up) add real multi-VM and heavy-container headroom. The real ceiling is RAM: containers idle in tens of MB each, VMs reserve gigabytes each, and base 2–4GB configs are the bottleneck. And often the honest answer is a separate mini PC for compute plus a simple NAS for storage.
The one thing to know: Whether a NAS can run Docker containers and virtual machines is set mostly by its CPU class and RAM, not the marketing. The Intel Celeron/N-series and low-power AMD chips in these boxes handle a handful of lightweight Docker containers (Pi-hole, a *arr stack, small databases) comfortably with 4–8GB RAM; running full virtual machines, or many heavy containers at once, wants a stronger CPU and 8–16GB+. ARM-based budget NAS units and some entry models don't support VMs or full container platforms at all. If self-hosting is your goal, prioritize an x86 (Intel/AMD) NAS with expandable RAM.
What can each CPU class actually run?
Every spec sheet says "supports Docker" or "runs apps," but the classes behave categorically differently. Three tiers cover the whole home-NAS market:
- ARM entry class (budget 1–2 bay units, typically 1–2GB RAM): reliable file serving, media direct-play, backups — and at best a couple of very light containers, where the platform allows containers at all. No virtual machines, and the app ecosystems on these models are restricted further by the vendor. If self-hosting is any part of your plan, skip this class.
- Intel Celeron / N-series x86 class (J4125, N5105, N5095, N95, N100 — most of our picks): the Docker sweet spot. A Pi-hole, Home Assistant, the *arr media-management stack, Vaultwarden, a reverse proxy, and a small database run comfortably side by side, because idle containers are cheap. One light Linux VM is feasible if the RAM allows — which usually means an upgrade past the base configuration. These chips also carry Quick Sync-class iGPUs, which matters for the media crowd (below).
- Ryzen / Core class (Synology DS923+ band and up, and the larger prosumer boxes): genuine multi-VM hosts and heavy container fleets — the DS923+'s 32GB ECC ceiling is the tell. This is the class where "NAS as homelab server" stops being a stretch. The wrinkle: the DS923+'s Ryzen R1600 has no iGPU, so its extra CPU strength doesn't help hardware transcoding at all.
CPU class → workload: the capability table
| Class | Example picks | Docker containers | Virtual machines | Hardware transcode (iGPU) |
|---|---|---|---|---|
| ARM entry | Budget 1–2 bay units (not on our list) | A couple of light containers at best; often platform-restricted | ❌ None | Varies; often direct-play only |
| Celeron J4125 | Synology DS224+ | ✅ Handful of light containers (2GB base RAM is the squeeze; max 6GB) | ⚠️ Not realistic at this RAM ceiling | ✅ Yes (H.264/H.265) |
| Celeron N5105 / N5095 | QNAP TS-264, TS-464 · Asustor AS5404T | ✅ The Docker sweet spot (upgrade 4GB bases toward 16GB) | ⚠️ 1 light VM with a RAM upgrade | ✅ Yes |
| Intel N95 / N100 | TerraMaster F4-424 · UGREEN DXP2800 / DXP4800 | ✅ Sweet spot, with healthy 8GB DDR5 bases (16–32GB max) | ⚠️ 1 light VM comfortably at 16GB+ | ✅ Yes |
| Ryzen R1600 class | Synology DS923+ | ✅ Heavy container fleets (up to 32GB ECC) | ✅ Multiple VMs with a RAM upgrade | ❌ No iGPU — direct-play or a separate transcode box |
| Separate mini PC + NAS | The homelab-orthodox split | ✅ Best per dollar | ✅ Best per dollar (Proxmox etc.) | ✅ On Intel mini PCs |
Why is RAM the real ceiling, not the CPU?
The asymmetry that decides everything: containers are RAM-cheap, VMs are RAM-expensive. A container shares the host's kernel, so an idle lightweight service — Pi-hole, Vaultwarden, a reverse proxy — commonly sits in the tens of megabytes; a half-dozen light containers can fit in under 1GB on top of the NAS OS. A virtual machine boots an entire guest operating system and reserves its memory whether busy or not: 1–2GB for a minimal Linux server, realistically 4GB+ for Windows, plus the NAS OS's own headroom. That's why a Celeron box that shrugs off ten containers chokes on its second VM — and why base 2–4GB configurations are the practical bottleneck long before the CPU is.
RAM upgradeability varies sharply by model class and is worth checking before you buy. Entry Synology units (like the DS224+) often have a small amount soldered plus one SODIMM slot with a modest official maximum (e.g. 6GB). Mid boxes (QNAP TS-x64, TerraMaster, UGREEN) typically take a single DDR4/DDR5 SODIMM up to 16GB, and prosumer boxes like the DS923+ reach 32GB of ECC. More RAM mainly helps caching, many simultaneous apps, containers, and VMs — not raw single-user file speed. Match RAM to how many services you'll run, and confirm the official maximum (unofficial higher configs sometimes work but aren't guaranteed).
Upgradeability among our picks, per the spec sheets:
- Synology DiskStation DS224+: 2GB onboard, one SODIMM slot, official max 6GB — enough for light Docker, not for VMs.
- Synology DiskStation DS923+: 4GB ECC base, expandable to 32GB ECC — the biggest ceiling here, matching its multi-VM ambitions.
- QNAP TS-264 / TS-464: 8GB and 4GB DDR4 bases respectively, both expandable to 16GB — budget the upgrade on the TS-464 if containers/VMs are the plan.
- TerraMaster F4-424: 8GB DDR5 base, expandable to 32GB — the most VM-ready RAM ceiling in the value tier.
- Asustor AS5404T (Nimbustor 4 Gen2): 4GB base, expandable to 16GB.
- UGREEN NASync DXP2800 / NASync DXP4800: 8GB DDR5 bases, expandable to 16GB via SODIMM.
The iGPU wrinkle: what about Plex/Jellyfin transcoding?
The media-server crowd has one extra spec to check, and it cuts against raw CPU class. Hardware transcoding in Plex or Jellyfin leans on an Intel Quick Sync-class integrated GPU, which converts video with a fraction of the CPU load of software transcoding. The Celeron/N-series picks here — DS224+ (J4125), QNAP TS-x64 (N5105/N5095), TerraMaster F4-424 (N95), Asustor AS5404T (N5105), UGREEN NASync (N100) — all have it. The Synology DS923+'s Ryzen R1600 does not: no integrated GPU at all, which its spec sheet's strength elsewhere doesn't fix. It's the known tradeoff on that box — stronger for VMs, a poor choice for hardware transcoding.
The honest framing, though: most home streaming never transcodes. Modern TVs and streaming boxes direct-play the common codecs, in which case the NAS just serves the file and any class handles it. Transcoding matters when you stream remotely at reduced bitrates, serve old or mixed client devices, or burn in subtitles. Decide which user you are before you let the iGPU decide your purchase.
Does the NAS operating system matter for Docker and VMs?
Yes, categorically. On x86 hardware every major platform ships a container runtime, but the maturity differs: Synology DSM pairs Container Manager (Docker) with Virtual Machine Manager and the deepest documentation; QNAP counters with Container Station and Virtualization Station; Asustor's ADM and TerraMaster's TOS offer Docker with smaller ecosystems and thinner documentation; UGREEN's young UGOS Pro includes Docker but its long-term track record is still being written. TerraMaster and UGREEN both openly support installing TrueNAS or another third-party OS on their hardware, which replaces the vendor app story with a proven community one. ARM entry models are restricted at the platform level as well as the hardware level — many simply can't run these platforms.
The honest alternative: a mini PC for compute, a NAS for storage
Before you buy a bigger NAS to chase VM headroom, price the homelab-orthodox split: a small x86 mini PC running Proxmox or plain Docker for compute, next to a simpler NAS that only stores. The mini PC route buys dramatically more CPU and RAM per dollar than any turnkey NAS upgrade, keeps your storage appliance boring and reliable, and means rebooting a broken experiment never takes your files offline. The NAS-only route wins on one box, one OS, one power budget, and vendor-supported simplicity. Rule of thumb: modest self-hosting on the NAS is great; the moment multiple VMs are the actual goal, separate compute usually beats a bigger NAS. Full tradeoff: DIY TrueNAS vs Synology.
Which picks fit which self-hosting plan?
- Light Docker, appliance-first — Synology DiskStation DS224+: the polished-DSM path for a few containers alongside photos and backups; the 2GB base (6GB max) is the hard limit, so keep ambitions light. Check price on Amazon →
- Docker sweet spot with an upgrade path — QNAP TS-464: N5095, dual 2.5GbE, NVMe slots, and a PCIe slot; upgrade the 4GB base RAM if you'll run many apps or a VM. Check price on Amazon →
- Most VM-ready value hardware — TerraMaster F4-424: N95 with 8GB DDR5 expandable to 32GB, and openly TrueNAS-friendly if you outgrow TOS. Check price on Amazon →
- Modern N100 value — UGREEN NASync DXP4800: N100 + 8GB DDR5 + dual 2.5GbE is a strong Docker platform; weigh UGOS Pro's youth, or plan on TrueNAS. Check price on Amazon →
- Multi-VM turnkey — Synology DiskStation DS923+: Ryzen class, up to 32GB ECC, Virtual Machine Manager under DSM — the strongest turnkey VM host here. Remember: no iGPU, so it's the wrong box if hardware transcoding is on your list. Check price on Amazon →
Related reading
Frequently Asked Questions
It depends almost entirely on CPU class and RAM, not marketing. ARM-based budget NAS units handle file serving plus a couple of light containers at best, and generally can't run VMs or full container platforms. x86 Intel Celeron/N-series boxes (N5105, N5095, N95, N100 class) are the Docker sweet spot: Pi-hole, Home Assistant, the *arr stack, Vaultwarden-class services run comfortably, and one light VM is feasible if you upgrade the RAM. Multi-VM or heavy container fleets want the Ryzen/stronger-CPU class with 16–32GB RAM, or a separate mini PC.
Far less than people fear. Idle lightweight containers commonly sit in the tens of megabytes each — Pi-hole, Vaultwarden, small utility services — so a half-dozen light containers can fit in well under 1GB on top of the NAS OS. Heavier apps (Home Assistant with many integrations, media indexers, databases) run in the hundreds of MB. That's why even a 4–8GB x86 NAS makes a capable Docker host. VMs are the opposite story: each VM reserves gigabytes up front.
Plan in gigabytes per VM, reserved whether the VM is busy or not. A minimal Linux server VM wants 1–2GB to be comfortable, a Windows VM realistically 4GB+, and the NAS operating system needs its own headroom on top. That's why base 2–4GB configurations are the real bottleneck: on a 4GB box, one VM plus the OS is already tight. If VMs are part of the plan, buy a NAS with a SODIMM slot and budget the RAM upgrade on day one — check the model's official maximum.
Only if you'll transcode. If every player on your network direct-plays the files (most modern TVs and streaming boxes handle common codecs), the CPU barely works and no iGPU is needed. Transcoding — remote streaming at lower bitrates, old or mixed client devices, burned-in subtitles — is where hardware acceleration matters: Intel Celeron/N-series chips (J4125, N5105, N95, N100) include Quick Sync-class iGPUs that transcode efficiently, while the Synology DS923+'s AMD Ryzen R1600 has no iGPU at all and is a poor transcoding choice despite being the stronger CPU for VMs.
On x86 hardware, all the major platforms ship a container runtime: Synology DSM has Container Manager (Docker) plus Virtual Machine Manager, QNAP has Container Station and Virtualization Station, Asustor ADM and TerraMaster TOS offer Docker apps, and UGREEN's UGOS Pro includes Docker support (its ecosystem is younger). TerraMaster and UGREEN boxes also openly support installing TrueNAS or other third-party OSes, which brings full-featured apps/VM tooling. ARM entry models are far more restricted — many can't run these platforms at all.
Often the mini PC wins. The homelab-orthodox split is storage on the NAS, compute on a small x86 mini PC running Proxmox or Docker: you get far more CPU and RAM per dollar than any turnkey NAS upgrade, the NAS stays a simple, reliable storage appliance, and rebooting your experiments never takes your files offline. Buying a bigger NAS makes sense when you want one box, one OS, and modest self-hosting; buying compute separately makes sense the moment VMs and heavy services are the actual goal.
How we work
We're a research-based site: we analyze manufacturer specifications, platform documentation, and container/VM engineering rather than lab-testing every enclosure. We report CPU classes, RAM ceilings, and categorical platform support, never guarantees — verify current specs and official RAM maximums on the manufacturer's page, and remember that no amount of compute changes the storage rules: RAID is not a backup. Read our full methodology →