SecureNAS Hub

NAS Guides · Published 2026-11-07

Synology Container Manager: How to Use Docker and Docker Compose

Illustrative image: Synology concept scene
Illustrative image: Synology concept scene

Direct answer up front, then the trade-offs that matter. This page covers synology container manager and answers: how to use synology container manager.

By Anne · Storage and Home Tech Editor

Beat: Phone photo backup · How we review

Quick Answer

Container Manager is Synology's DSM package for running Docker containers and Compose projects. Install it from Package Center, create a folder under /volume1/docker/, then use the Project tab to build a docker-compose.yml. One detail breaks most first attempts: relative volume paths from upstream documentation do not work on a Synology NAS, so every local path must be absolute.

Key Takeaways

Why your old Docker tutorial stopped working

You follow a guide written for a Synology NAS, open Package Center, and there is no Docker icon. Nothing was deleted. The package was renamed to Container Manager in DSM 7.2, and the interface was rebuilt around it, so menu labels and setting locations changed even though the underlying engine kept running the same containers and images (WunderTech, accessed 2026-11-07). That mismatch is the pain point. A tutorial can be entirely correct about Docker and still be unusable on your screen, because the steps point at controls that no longer exist under those names.

The second half of the confusion is version drift. The Docker engine moved from the 20.10 era to 24.x, and Compose became a built-in feature rather than something you installed over SSH (WunderTech, accessed 2026-11-07). Older guides therefore spend paragraphs on SSH setup that modern DSM does not need. We could not verify an official, complete list of every DSM version and Synology model that supports Container Manager, so treat any model-specific claim you read elsewhere as unconfirmed until you check the package page for your own unit.

The practical consequence is narrow and fixable. You do not need to relearn Docker. You need to translate three things into the DSM interface: where a Compose file lives, how a volume path is written, and which port the NAS has already taken. Everything else from the upstream documentation still applies, including the container's own environment variables and image name.

Container Manager is worth learning if you plan to run more than two or three services, because a Compose file records the full configuration in one place. It is overkill if you only want one first-party app from Package Center. That trade-off is the whole decision, and the rest of this guide works through the translation in the order you will actually hit it.

What Container Manager is, and what it replaced

Container Manager is a DSM package that runs Docker containers on a Synology NAS, with a Project tab for multi-container applications defined in a Compose file (Synology Knowledge Center, accessed 2026-11-07). Synology's own description of the package says the Project dashboard lets you create, operate and manage projects using Compose files, while the Image dashboard tracks image status, size and version updates (Synology (Official), accessed 2026-11-07). The package also exposes an Overview dashboard with container, CPU, RAM and network usage, which is the first place to look when a container starts consuming more memory than the NAS can spare.

Installing it creates a shared folder called docker, and most setups start at /volume1/docker/. If the folder sits on another volume, the path becomes volume2 or volume3 instead; Control Panel's Shared Folders list tells you which one applies (WunderTech, accessed 2026-11-07). There is no separate "Container Manager" folder, so the docker folder stays the root of your project tree. Write that path down before you open the wizard, because every volume line in your Compose file will use it.

The interface splits into tabs with distinct jobs: Registry searches Docker Hub and pulls images, Image lists what is downloaded and flags updates, Container shows running services, Network manages Docker networks, and Log records package events (WunderTech, accessed 2026-11-07). Project is the one worth using by default. It stores the entire configuration as a docker-compose.yml in a folder you choose, so moving the stack to a mini PC later means copying one folder and running one command (WunderTech, accessed 2026-11-07). A container built click by click in the GUI has no such file.

We should be plain about the limit of this article. The first-party data we hold is a price and spec ledger. We did not benchmark container startup, measure throughput, or run a stress test on any of these units. Every performance-adjacent statement below is either a published specification from a vendor page or a reproducible configuration step, not a measurement. If a number is not in the ledger or in a named source, we say so rather than filling the gap.

Create your first project, step by step

Synology documents the creation wizard in three fields. Click Create, then set Project Name, Path (the working directory), and Source — either upload a docker-compose.yml or create one with the built-in editor. You can enable a web portal to reach the project through Web Station, confirm the summary, click Done, and choose whether to start immediately (Synology Knowledge Center, accessed 2026-11-07).

Project Name is not a cosmetic label. Compose derives its default project name from the directory containing the Compose file, and the name must contain only lowercase letters, decimal digits, dashes and underscores, beginning with a lowercase letter or decimal digit (Docker Documentation, accessed 2026-11-07). A name like Photo_Backup fails that rule. The same documentation gives the precedence order: the -p flag, then the COMPOSE_PROJECT_NAME environment variable, then a top-level name: attribute in the Compose file, then the project directory base name, then the current directory (Docker Documentation, accessed 2026-11-07). Inside DSM you mostly interact with the first field of the wizard, so pick a short lowercase name and keep the folder name identical.

Build the folder first, in File Station, before you touch the wizard. Give each project its own subfolder with its own Compose file rather than piling everything into the root of docker (WunderTech, accessed 2026-11-07). This is not tidiness for its own sake. The Clean action removes resources created by that project's Compose file, and a shared root makes it much harder to tell which folders belong to which stack. If you copy a Compose example that still begins with a version: line, deleting that line is safe — the field is obsolete in current Compose (WunderTech, accessed 2026-11-07), a point also reflected in Docker's own move toward the Compose Specification.

Here is the action set Synology lists for an existing project, with the underlying commands from the same help page (Synology Knowledge Center, accessed 2026-11-07):

ActionWhat Synology says it runsEffect on your data
Builddocker-compose up --build --no-startBuilds images; no containers started
Startdocker-compose startStarts existing containers; requires a prior build
Stopdocker-compose stopStops containers without removing them
Restartdocker-compose restartRestarts stopped and running containers
Cleandocker-compose downStops containers and removes containers, networks, volumes and images
Delete—Deletes all containers and the data of the project

Read the Clean row twice. Synology's wording explicitly includes volumes in what down removes, and the Delete row separately removes all containers and project data (Synology Knowledge Center, accessed 2026-11-07). Those are not synonyms for Stop. Use Stop when you want the stack to come back exactly as it was; use Clean only when you intend to rebuild from scratch and your persistent data is backed up somewhere outside those paths. The catch is that a folder mounted with a bind path under /volume1/docker/ is your data on the NAS, while a named volume declared only inside the Compose file is managed by Docker — a distinction worth checking in your own YAML before you press Clean.

After creation, the Details view offers Containers, Statistics, YAML Configurations and Settings. YAML Configurations lets you edit the Compose file in place and deploy the project with the new settings (Synology Knowledge Center, accessed 2026-11-07). That is the normal loop: edit, deploy, check Statistics for CPU, memory and network, then edit again.

The volume path trap that breaks most projects

Upstream Compose examples use relative bind paths such as ./etc-pihole:/etc/pihole. Those do not work on a Synology NAS (WunderTech, accessed 2026-11-07). In a volume line, the left side is a path on the NAS and the right side is a path inside the container; you rewrite the left side as an absolute path including the volume number and leave the right side alone. Container Manager will not create the subfolders for you, so every directory named on the left must already exist in File Station or the project fails to start (WunderTech, accessed 2026-11-07). WunderTech reports that a missing folder or a port conflict accounts for almost every failed project creation.

A rewritten example from that source looks like this (WunderTech, accessed 2026-11-07):

`yaml

services:

jellyfin:

image: jellyfin/jellyfin

container_name: jellyfin

network_mode: 'host'

volumes:

restart: 'unless-stopped'

`

Create jellyfin, then config, cache and media, before you deploy. The three mounted folders hold the state you care about; everything else is configuration you can rebuild (WunderTech, accessed 2026-11-07). That is the backup boundary. Back up the mounted folders, not the image. If you create containers through the GUI instead, the same three settings appear as separate wizard fields — Volume, Ports and Environment Variables — with a read-write or read-only toggle on each mount (WunderTech, accessed 2026-11-07).

One more setting deserves suspicion. The GUI offers "execute container using high privilege", which runs the container as root. Keep it off unless the image documentation explicitly requires it (WunderTech, accessed 2026-11-07). A container that only needs to write to its own mounted folder has no reason to hold that level of access to the NAS.

Port 80, host networking, and where macvlan stops helping

Ports map the same way volumes do: a local NAS port points at a container port. DSM already uses port 80 for its own reverse proxy, so a container that wants port 80 will collide with the system (WunderTech, accessed 2026-11-07). Map it to a free local port such as 8080 instead. You would then reach the service at an address of the form http://192.168.1.50:8080 — example address, do not use directly; substitute your own NAS address and the port you chose. The cost is an odd-looking URL, and for most services that is the entire cost.

If you set a container to host networking, the port settings disappear, because the container shares the NAS network stack and there is nothing left to map (WunderTech, accessed 2026-11-07). That behaviour is expected, not a bug, but it also means the container can collide with DSM on any port it claims. Pi-hole is the usual example, since its admin interface wants port 80 (WunderTech, accessed 2026-11-07).

The alternative is a macvlan network, which gives a container its own IP address and its own full port range. It is created over SSH with docker network create -d macvlan, using your own parent interface, subnet, gateway and free IP address (WunderTech, accessed 2026-11-07). The limits are sharp: a macvlan interface can only be assigned to one container, and the NAS itself cannot talk to containers on that interface by default, so you keep a bridge network alongside it for NAS-to-container traffic (WunderTech, accessed 2026-11-07). Bonded interfaces need experimentation. Compared with simply changing the local port, macvlan buys clean port numbers at the price of extra networking you now have to maintain.

Security guidance from the same source is blunt: do not port forward containers to the internet directly, use a reverse proxy or a VPN for outside access, and keep DSM current (WunderTech, accessed 2026-11-07). That advice is general, not a guarantee about any specific setup. We could not verify current DSM firewall defaults for every model, so check your own Control Panel before exposing anything.

Which Synology models have enough headroom

Memory is the constraint that decides how many containers you can run, and the ledger we maintain tracks it per model. Here is the comparison table generated from that ledger. All figures carry the ledger's own source links, listed below the table, and the check dates shown in each cell (spec ledger, accessed 2026-11-07).

FieldSynology DS225+ (2025)Synology DiskStation DS925+Synology DiskStation DS923+Synology DiskStation DS1525+
Price (tracked)Amazon $364.99 (2026-10-02, stale)Amazon $749.76 (2026-10-02, stale)US street (diskless) $599 (2026-10-02, stale)Amazon $1309.99 (2026-10-02, stale)
Drive bays (SATA)2 bays4 bays4 bays5 bays
M.2 NVMe slots0 slots2 slots2 slots2 slots
Max bays with expansion7 bays9 bays9 bays15 bays
Hot-swap baysYesYesYesYes
CPUIntel Celeron J4125AMD Ryzen V1500BAMD Ryzen R1600AMD Ryzen V1500B
CPU cores4 cores4 cores2 cores4 cores
Installed RAM2 GB4 GB4 GB8 GB
Max RAM6 GB32 GB32 GB32 GB
RAM slots1 slot2 slots2 slots2 slots
ECC RAMNoYesYesYes
1GbE ports1 port—2 ports—
2.5GbE ports1 port2 ports—2 ports
PCIe slots——1 slot1 slot
USB ports2 ports2 ports2 ports2 ports
Form factorDesktop towerDesktop towerDesktop towerDesktop tower
Weight1.3 kg2.26 kg2.24 kg2.67 kg
Internal filesystem—Btrfs, ext4Btrfs, ext4Btrfs, ext4
Warranty3 years3 years3 years3 years

_Sources: Synology DS1525+ product page · Synology DS923+ product specification (PDF) · Synology official comparison (DS225+) · Synology official comparison (DS925+) (accessed 2026-11-07)._

_— = no verified figure in the ledger for that field. Prices marked stale are historical readings from 2026-10-02, not current prices._

Read the Installed RAM row against the Max RAM row. The DS225+ ships with 2 GB and tops out at 6 GB across one slot, while the DS925+ and DS923+ start at 4 GB and reach 32 GB across two slots; the DS1525+ starts at 8 GB (spec ledger, accessed 2026-11-07). A handful of small containers fit in 2 GB. A media server plus a database plus a monitoring stack is a different proposition, and no configuration trick in Container Manager adds physical memory. Our take: if you already own a 2 GB unit, start with one container and watch the Overview RAM figure; if you are buying specifically to run a stack, the machines with two RAM slots give you an upgrade path instead of a ceiling.

Prices are the awkward part of this table. Four readings are stale, so we will not present them as current. The one fresh entry in our price ledger is different: Synology listed the DS224+ at $299.99 in its launch announcement, checked 2026-10-30 (Synology (Official), accessed 2026-11-07). That is a launch MSRP, not a live retail quote, and we could not verify current pricing for any of the four models in the table. If you need a number for a purchase decision today, check the retailer yourself and write down the date. We would rather leave that blank than print a plausible-looking figure.

Updating a project without losing your data

Containers are replaced rather than patched. The Compose path is two commands, run from the folder holding that project's docker-compose.yml because Compose works against the file in the current directory (WunderTech, accessed 2026-11-07):

`bash

sudo docker compose pull

sudo docker compose up -d

`

Note the space in docker compose. The older hyphenated docker-compose form is no longer the current invocation, and Compose ships as part of Docker itself in current Container Manager, so there is nothing extra to install (WunderTech, accessed 2026-11-07). Pull fetches the newer image; up -d rebuilds the container from it. Back up the mounted folders first, because the folders are where your persistent state lives (WunderTech, accessed 2026-11-07). If an update misbehaves, pinning the image to an older tag in the same file and bringing the project up again is the rollback path — one reason a Compose file beats a hand-built GUI container, where you would be re-entering every volume and variable.

Updating deserves a decision, not a reflex. If the container is exposed to the internet or the release fixes a security flaw, update. If it runs locally and has been stable for months, weigh a few new features against the chance of introducing a problem you did not have (WunderTech, accessed 2026-11-07). SSH access, if you need it for command-line work, is enabled under Control Panel → Terminal & SNMP, and the Synology firewall must allow port 22; commands such as sudo docker container ls and sudo docker exec -it CONTAINER_ID bash are how you inspect a running container, with sh as the fallback when the image has no bash (WunderTech, accessed 2026-11-07). Anything changed inside a container but outside a mounted folder disappears when the container is replaced (WunderTech, accessed 2026-11-07).

Common mistakes

Who should skip this, and who should not

Choose Container Manager with Compose projects if you run three or more self-hosted services, if you expect to migrate the stack to a Proxmox host or a mini PC later, or if you want the whole configuration in a file you can back up. The portability argument is concrete: a Compose folder is a format any Docker host understands, whereas a first-party package keeps its data where the vendor decided to put it (WunderTech, accessed 2026-11-07). Synology's DS923+ and DS925+ are the ledger entries with two RAM slots and a 32 GB ceiling, which is the headroom a growing stack needs (spec ledger, accessed 2026-11-07).

Skip it if you only need Synology Drive, Photos or one surveillance app. Package Center installs those with less setup, and the container ecosystem's flexibility is worth nothing to someone who will never use it. Skip it too if your unit has 2 GB of soldered RAM and your plan involves a database plus a media indexer; the DS225+ tops out at 6 GB on a single slot, and no YAML edit changes that (spec ledger, accessed 2026-11-07). We could not verify a current retail price for that model, so we will not name one.

One honest limit on the whole exercise. This is a configuration guide built from vendor documentation and one independent tutorial, not a hardware review. The specs above come from a tracked ledger with vendor links; the steps come from Synology's help page; the traps come from WunderTech's walkthrough. None of it is a measurement from our own bench, and we have marked every place where the record runs out. Start with one container you actually want, get its volume paths right, and let the second project be the test of whether this workflow fits you.

Frequently Asked Questions

How do I install Container Manager on a Synology NAS?

Open Package Center in DSM and install Container Manager from there. The package replaces the older Docker package rather than sitting beside it, and existing containers survive the transition (WunderTech, accessed 2026-11-07). Installation creates a docker shared folder, which is where project folders should live. We could not verify the complete supported-model list, so confirm the package is offered for your specific unit in Package Center first.

How do I create a Docker Compose project in Container Manager?

Click Create in the Project tab, then set Project Name, Path and Source. Source accepts an uploaded docker-compose.yml or one written in the built-in editor; you can also enable a web portal through Web Station before clicking Done (Synology Knowledge Center, accessed 2026-11-07). Build each project in its own subfolder under /volume1/docker/, and create that folder in File Station before you start the wizard.

Why does my Compose project fail to start on a Synology NAS?

The two common causes are a volume path that does not exist and a port conflict (WunderTech, accessed 2026-11-07). Upstream examples use relative paths, which DSM does not resolve; rewrite the left side of each mount as an absolute path with the volume number, and create every folder first. Then check whether the container wants port 80, which DSM already uses for its reverse proxy, and remap it to a free local port.

How do I stop Container Manager without deleting my containers?

Select the project and use Stop, which runs docker-compose stop and leaves the containers in place so you can start them again without rebuilding (Synology Knowledge Center, accessed 2026-11-07). Do not use Clean for this. Clean runs docker-compose down and removes containers, networks, volumes and images created by that project's Compose file, while Delete removes all containers and project data.

How do I update containers in a Compose project?

From the folder containing docker-compose.yml, run sudo docker compose pull followed by sudo docker compose up -d (WunderTech, accessed 2026-11-07). Back up the mounted folders before you start. If the new image causes trouble, pin an older image tag in the Compose file and bring the project up again. Compose ships inside Docker in current Container Manager, so the old hyphenated binary is not required.

Can I use Docker Compose on DSM 7.1 or earlier?

Compose became a built-in feature of the package with the DSM 7.2 change, and the Project tab arrived with that release (WunderTech, accessed 2026-11-07). Earlier versions used the Docker package and required SSH-based Compose setup. We could not verify the exact behaviour of every 7.1 point release, so check Synology's documentation for your installed DSM version before following a modern Project-tab guide.

Sources

Run your own 5-year cost comparison with the on-site calculator

Every figure above is attributed in the Sources list — put your own drive count and subscription tiers into the calculator to see where you land.

Open the cost calculator →

Related reading

Was this article helpful?

One tap, no account and no comment box. It tells us which guides are actually worth updating.

Need help with a specific setup?

Storage choices depend on your drives, your budget and how many people share the box. Tell us what you are building and we will point you at a configuration that fits — no obligation, no sales script.

Affiliate Disclosure: SecureNAS Hub may earn a commission from qualifying purchases made through links on this page, at no extra cost to you. Facts and figures are attributed in the Sources list; nothing on this page is a fabricated test result. See our full disclosure. Product images are either supplied by the manufacturer or clearly labelled as illustrative renders; each one is captioned accordingly. Last reviewed 2026-11-07.