NAS Codex › Synology › Synology Container Manager container won't start or shows an error

Synology Container Manager container won't start or shows an error

Container Manager runs containers on DSM from images, such as those on Docker Hub. When a container won't start, or the Overview page shows Warning or Error, Synology's DSM 7 help points to a short list of places to look: the container's own log and the Container Manager log, the ports the container uses (a conflict with DSM services may cause service errors), and the image and settings the container was created with.

Written against: DSM 7 with Container Manager (Synology DSM 7 help: Container Manager Container, Overview and Log; Synology KB: What network ports are used by services on my Synology system?). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.

Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.

Fast Answer

In Container Manager > Container, select the container, click Details and open Log to read its activity log. Then check its ports: Synology says to pick ports that other DSM services don't use, because a port conflict may cause service errors (DSM itself uses 5000 and 5001, Web Station 80 and 443). If the settings are right and an image from Docker Hub still won't work, Synology suggests trying a different image.

1. Check the status on the Overview page

Open Container Manager > Overview. Synology lists these service statuses:

The same page shows the resource usage of running projects and containers, and an Image Information section with Update (update images to the latest version, if available) and Remove Unused Images.

2. Read the logs

  1. Go to Container Manager > Container and select the container.
  2. Click Details. General shows its information, Statistics its CPU, memory and network use, and Log its activity log. You can search the log or click Export to save it as HTML or CSV.
  3. For Container Manager itself, open the Log page. Filter by Info, Warning or Error, search, refresh, or export as HTML or CSV.

Synology notes that Clear on the Log page deletes all log records and cannot be undone, so export first if you may need them.

3. Look for a port conflict with DSM

In its container help, Synology says to select container ports that are not used by other DSM services, because a port conflict may cause service errors, and points to its list of DSM ports. A few entries from that list:

Compare the local ports in the container's settings with that list and with the services you run. The network mode matters too: Synology's help says a container can join one or more bridge networks or use the same network as the Docker Host (DSM).

4. Check the image and the container settings

Synology's help on creating a container lists what each setting is for:

Two notes from the same page: the default time zone of most containers is UTC (set the TZ environment variable to change it), and resource limitation cannot be disabled once it was enabled when the container was created. And if you can't create a container from a Docker Hub image even though the settings are correct, Synology says to try a different image, because Docker Hub images are uploaded by developers and their quality can't be guaranteed.

5. Restart, reset or rebuild the container

Select the container and click Action to Start, Stop, Force stop, Restart or Reset it. Other options on the same page:

When to stop and get help

Export the logs before you click Clear on the Log page: Synology says the deletion is irreversible. Export a container and its settings before you delete it, so you can import them again.

Questions

Where are the logs for a Synology Container Manager container?

In Container Manager > Container, select the container, click Details and open Log. You can search it or export it as HTML or CSV.

Can a port conflict stop a container on Synology?

Synology says to choose container ports that other DSM services don't use, because a port conflict may cause service errors. DSM uses 5000 and 5001.

Why does my Synology container show the wrong time?

Synology says most containers default to UTC. Set the TZ environment variable to change the container's time zone.

Sources

Every fact on this page comes from the vendor documents below, opened on 2026-11-18.