Synology sells the dream in containers and the reality in gigabytes. DSM takes its share of memory first, every container takes its own slice, and when the plate is empty the NAS does not slow down gracefully — it swaps, stutters, and sometimes kills the very app you wanted. Here is how to count honestly.
RAM is the one resource you cannot negotiate with. CPU overload makes things slow; memory overload makes things stop. On a Synology NAS the arithmetic is unforgiving: many models ship with 2 GB of RAM, some value models with less, and certain models have that memory soldered — the number you buy is the number you die with. Other models, especially in the Plus series, accept more. Every container you run is paid for out of the same pool that DSM itself drinks from, and the pool is smaller than the box suggests.
Before planning anything, spend two minutes with your own machine's figures — they are the only ones that describe your NAS.
Every app's download page or documentation states its appetite, but the pattern is consistent enough to plan by.
Whether RAM is a wall or a door depends on the model. Many Plus series models have a memory slot (sometimes two) and accept larger modules, within Synology's stated maximum for that model. The ARM value models that support Container Manager — the DS124, DS223, DS423 class — have their memory fixed at the factory, commonly 1 or 2 GB.
Check your model's specification page for the words memory slot or its absence before building plans on an upgrade. If a slot exists, more RAM is the single cheapest container upgrade there is. If it does not, your plan must fit the memory you have — or the heavy apps must live on a different machine, with the NAS doing what it does best: storing their data.
A memory-starved NAS rarely says so in words. It shows you instead:
The cure is arithmetic, not settings: remove a tenant, shrink a tenant, add memory if the model allows, or move the heavy tenant to a machine with a bigger pool.
For a typical 2 GB home machine, the stack that lives happily ever after looks like this: DSM's baseline, three or four light apps, and one medium app — with the graph checked after each addition and a day of normal life allowed to pass before the next. Add apps one at a time, like medicines, so that if something turns strange you know exactly which arrival to question. And leave headroom: a NAS at 70 percent memory is a tool; a NAS at 98 percent is a suspense story.
The full Docker on Synology NAS installation, shown live on a real NAS from package install to a running container.
▶️ Watch Full VideoIt depends on the model. Many Plus series models have a memory slot and accept larger modules up to Synology's stated maximum for that model. The ARM value models that support Container Manager generally have fixed, soldered memory that cannot be changed. Check your exact model's specification page for a memory slot before planning an upgrade.
The most common reason on a small NAS is memory pressure: when the system runs out of RAM — often while backups or indexing are also running — it may stop a container to protect DSM itself. Check the memory graph in Resource Monitor for the same hours, and look at how much the container and everything else were using together.
There is no honest single number, because containers differ enormously. Several light apps at 100 to 300 MB each can share a 2 GB NAS comfortably with DSM. Add one heavy app needing a gigabyte or more and the same NAS may hold nothing else. Watch each container's real usage in Container Manager and budget from measurements, not from counts.