[BUG] - Could not bring Docker Engine back online after bringing synology version to 27.5.1

[BABACHAN]

Describe the bug

I restarted all container to use local logger.

Tried to install v27 via:
sudo ./syno_docker_update.sh -d 27.5.1 -c 2.33.0 update

No errors until at the end it reports that deinge cannot be brought online.

Even a reboot of NAS did not help.

DSM 1515+
DSM version 7.1.1-42962 update 9

To reproduce

sudo ./syno_docker_update.sh -d 27.5.1 -c 2.33.0 update

Expected behavior

Working update

Log file

Update Docker Engine and Docker Compose on Synology to target version

Current DSM version: 7.1.1
Current Docker version: 20.10.3
Current Docker Compose version: 1.28.5
Current containerd version: 1.4.3
Current runc version: 1.0.0
Target Docker version: 27.5.1
Target Docker Compose version: 2.33.0

WARNING! This will replace:
  - Docker Engine
  - Docker Compose

Are you sure you want to continue? [y/N] y
Step 1 from 11: Backing up current Docker binaries (/volume1/homes/nly95861/synology-docker/docker_backup_20260808_144614.tgz)
bin/
bin/docker-compose
bin/containerd-shim-runc-v1
bin/auplink
bin/containerd-shim
bin/docker-proxy
bin/containerd
bin/docker
bin/containerd-stress
bin/runc
bin/docker-init
bin/ctr
bin/dockerd
bin/containerd-shim-runc-v2
dockerd.json
start-stop-status
Step 2 from 11: Checking for / Installing iptables modules.
Step 3 from 11: Downloading target Docker binary (https://download.docker.com/linux/static/stable/x86_64/docker-27.5.1.tgz)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 72.6M  100 72.6M    0     0  61.5M      0  0:00:01  0:00:01 --:--:-- 61.6M
Step 4 from 11: Downloading target Docker Compose binary (https://github.com/docker/compose/releases/download/v2.33.0/docker-compose-linux-x86_64)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 70.1M  100 70.1M    0     0  49.7M      0  0:00:01  0:00:01 --:--:-- 59.1M
Step 5 from 11: Stopping Docker service
{"action":"stop","beta":false,"error":{"code":0},"finished":true,"language":"enu","last_stage":"stopped","package":"Docker","pid":25138,"scripts":[{"code":0,"message":"","type":"stop"}],"stage":"stopped","status":"stop","status_description":"translate from systemd status","success":true,"username":"","version":"20.10.3-1308"}
Step 6 from 11: Extracting target Docker binary (/tmp/docker_update/docker-27.5.1.tgz)
docker/
docker/runc
docker/containerd
docker/docker-init
docker/dockerd
docker/containerd-shim-runc-v2
docker/docker-proxy
docker/docker
docker/ctr
Step 7 from 11: Installing binaries
Step 8 from 11: Configuring log driver
Skipping configuration in STAGE mode or TARGET mode
Step 9 from 11: Enabling IP forwarding
Added missing IP forwarding configuration to /var/packages/Docker/scripts/start-stop-status.
Step 10 from 11: Starting Docker service - May take a while.
   - timeout set to 13m based on 9 active containers
{"action":"start","beta":false,"error":{"code":272,"description":"Failed to run script, script=[start]"},"finished":true,"language":"enu","last_stage":"prepare_start","package":"Docker","pid":26235,"scripts":[{"code":1,"message":"","type":"start"}],"stage":"start_failed","status":"stop","status_description":"translate from systemd status","success":false,"username":"","version":"20.10.3-1308"}
ERROR: Could not bring Docker Engine back online

Docker daemon configuration

cat: /var/packages/ContainerManager/etc/dockerd.json: No such file or directory

Additional context

No response

[telnetdoogie]

try sudo cat /var/packages/Docker/etc/dockerd.json to provide your Docker Daemon config.

Since you're on 7.1.1 this may be related to a recent change of package detection / naming with Docker vs ContainerManager names / folders, or something in your container configs preventing startup.

Did you successfully migrate running containers away from the db logger?

Some more info from sudo journalctl or logs from /var/log/messages might help troublshoot.

For now, uninstall & reinstall ContainerManager from the package manager. Once it's up and running again, run the ./syno_docker_list_containers.sh script from the README instructions, and provide the output here.

[BABACHAN]

dockerd.json content
{ "data-root" : "/var/packages/Docker/var/docker", "group" : "administrators", "log-driver" : "local", "log-opts" : { "max-file" : "5", "max-size" : "20m" }, "registry-mirrors" : [], "storage-driver" : "aufs" }

Did you successfully migrate running containers away from the db logger?

Yes, all where db in the beginning. This is the overview now

`Container Compose_Location Logger

---

/dockge !---maybe_managed_by_portainer---! local
/gitea_db_1 !---maybe_managed_by_portainer---! local
/gitea !---maybe_managed_by_portainer---! local
/grafana !---maybe_managed_by_portainer---! local
/homeassistant !---maybe_managed_by_portainer---! local
/mosquitto !---maybe_managed_by_portainer---! local
/uptime-kuma !---maybe_managed_by_portainer---! local
/zigbee2mqtt !---maybe_managed_by_portainer---! local
/influxdb2 !---maybe_managed_by_portainer---! local
`
At first only dockge and homeassistent were "maybe_managed_by_portainter".

/var/log/messages is empty

After the failure the restore works fine. Except for the logger remain local.

[BABACHAN]

There is no longer an immediate need to get this working on my synology. I initially needed it to update homeassistent past 2026.2 due to the new docker image compression zstd, which is not supported on my old docker engine.
I found another workaround by re-compression. This works and is less invasive. So, I'm sticking to that solution.

Thank you for your time.

[bslatyer]

Further to this, I just spun up a DS1515+ and Home Assistant works (without errors) on 27.5.1 and the default shipping of 24.0.1.