Docker daemon fails to start on voxl

kiprock

I had a battery go pretty low and the system crashed while running mavros in docker last night, after reboot, docker deamon is not responding and I cannot see any images.

Eric Katzfey

@kiprock I would reflash the system, setup your IP connection, configure Docker and just verify that it works as expected.

kiprock

just looking at the logs, the docker deamon fails here:

level=fatal msg="Error starting daemon: Error initializing network controller: could not delete the default bridge network: network bridge has active endpoints"

Most forums suggest removing the docker network folder: rm -r /var/lib/docker/network

I did this but still having issues. Just curious if the modalAI setup stores docker files somewhere else?

Eric Katzfey

@kiprock Everything is stored on /data. But again, I would reflash and start over just to verify Docker operation.

kiprock

rm /data/network/files/local-kv.db

did the trick. Thanks for providing that missing piece of data!

shlee853

@kiprock Hi I have a exactly same issue.

I flashed image and reset factory configuration on my VOXL, but, It has still issue.

Did you resolve this problem?

Thanks,

kiprock

@Eric-Katzfey if you cannot start docker images, you can try the command above to clear them. Good luck.

Eric Katzfey

Thanks, but I think you meant to ping @shlee853

shlee853

@kiprock thank you for your reply
I’ll try it

shlee853

@shlee853

Great!

I resolved this problem as you mentioned.

yocto:/$ rm /data/network/files/local-kv.db
yocto:/$ voxl-configure-docker-support.sh 
Stopping original docker service
Enabling our own services docker-start & docker-prepare
starting docker-start.service
loading hello-world docker image
successfully loaded hello-world
starting docker-prepare service
Created symlink from /etc/systemd/system/default.target.wants/docker-autorun.service to /etc/systemd/system/docker-autorun.service.

done configuring voxl-docker-support

LucasW

@kiprock Thank you for this, that also solved the issue in my case.

To be a little more cautious, I simply renamed the existing file, which forced the generation of a new one when running the configuration script voxl-configure-docker-support.sh:

voxl:/data/network/files$ mv local-kv.db local-kv_DISABLED.db