Solved Docker package doesn't start anymore

Currently reading
Solved Docker package doesn't start anymore

38
9
NAS
DS209j | DS210j | DS410 | DS214 | DS216+II | DS916+
I just did an update of the Docker package to 18.09.0-0513
and now the package wont start anymore.

Not even if I try manually after a reboot:
Code:
ash-4.3# synoservicecfg --enable pkgctl-Docker
service [pkgctl-Docker] start failed, synoerr=[0x0000]

somewhere I read VPN Package blocks the new start ("Docker can't create a network for itself when starting if a VPN is running" Synology Community )
but stopping the VPN Server didnt help.

Any other ideas?
Thanks!
paradeiser
 
38
9
NAS
DS209j | DS210j | DS410 | DS214 | DS216+II | DS916+
just to let you know what caused the problem here a quick follow up

Synology support sent me this response after remote access:

Apparently the Network Database local-kv.db had been corrupted.

By renaming the File, Docker is not able to detect the existing corrupted Database and creates a new Database.

Docker was able to start with a new Database.

The Networksettings created in Docker previously will be lost however.

/case closed
 
Wow, glad they could sort it out. I never knew exactl where local metadata state was exactly stored. There are a couple of binary .db files in the root-data's subfolder. I probably would have deleted the whole root-data to reset the state to an empty state. Then I would have deployed all container from docker-compose.yml files again.

Learned something new today. Thanks for that :)
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Similar threads

Similar threads

Trending threads

Top