Mark Dumay

By the looks of it, the Docker binaries seem to be locked by another process. Normally the script stops the currently running Docker daemon before attempting to copy the new...

I see, that part was missing from your log file. :-) The script invokes `synoservicectl --stop pkgctl-Docker` to stop the Docker daemon from running. This is Synology's way to control...

Hi @fenio, I've added issue #45 to force stop the containers from the command line. The other issue regarding the log driver is a known issue, see #42.

Can you share the full log of the `syno_docker_update.sh` command you ran? And what is the current content of your `/var/packages/Docker/etc/dockerd.json` file?

Both the script and daemon configuration appear to be fine. Can you try stopping and restarting the container(s)? It seems to refer to the now obsolete db log driver.

Great! I'll add an instruction to the README too ;-)

hi @exotsk, to help me identify potential causes of your issue, would you mind submitting a new issue using the bug report template?

I have the same issue with Synology's Docker UI. Running `docker ps` from the terminal works fine, but the up time in Docker UI is garbage. Clicking on a container...

That's unfortunate. My NAS still uses EXT4, so I'm not able to reproduce your error. However, after some research, possibly changing the storage driver might help? I used Docker's [guide](https://docs.docker.com/storage/storagedriver/btrfs-driver/)...

Sorry to hear that @Zenedith. Would you happen to have a backup of `/var/packages/Docker/etc/dockerd.json` that you could share? Perhaps Synology's original configuration (prior to running the update with `synology-docker`) gives...