Docker daemon fails to start on voxl

[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

[José Quintanilla]

@modaltb I have a problem, after I write that line, the drone display a message that says: voxl:/$ voxl-configure-docker-suport.sh
bash: voxl-configure-docker-suport.sh: command not found
voxl:/$

[tom]

@José-Quintanilla Looks like you spelled it wrong

[tom]

@José-Quintanilla You can use [TAB] after you start writing a command to auto-fill

[José Quintanilla]

@tom I think it worked, thanks

[José Quintanilla]

@tom It wasn't that, because I need that especific line on my VOXL to work, so I can use properly the sdk

[tom]

@José-Quintanilla What is not working? Did you run voxl-configure-docker-support.sh?

[José Quintanilla]

@tom That's the line that doesnt let me run, my done say: voxl-configure-docker-support.sh: command not found

[tom]

@José-Quintanilla What release do you have installed, what does voxl-version say?

[José Quintanilla]

@tom If I recall is the 0.9 version

[tom]

@José-Quintanilla When you get a chance post the output of voxl-version. Also what hardware are you on?

[José Quintanilla]

@tom I confirm that is the voxl 0.9 version on a m500 hardware im using a voxl flight

[tom]

@José-Quintanilla I was asking because that command also lists installed packages, try without the .sh: voxl-configure-docker-support

[José Quintanilla]

@tom voxl:/$ voxl-version

system-image: 4.0.0
kernel: #1 SMP PREEMPT Thu Oct 13 17:57:05 UTC 2022 3.18.71-perf

hw version: VOXL

voxl-suite: 0.9.4

Packages:
Repo: http://voxl-packages.modalai.com/dists/apq8096/sdk-0.9/binary-arm64/
Last Updated: stat: cannot stat '/var/lib/opkg/lists/modalai': No such file or directory
stat: cannot stat '/var/lib/opkg/lists/modalai': No such file or directory
WARNING: repo file has changed since last update,
packages may have originated from a different repo
List:
apq8096-dfs-server 0.3.1
apq8096-imu-server 1.0.3
apq8096-libpng 1.6.38-1
apq8096-system-tweaks 0.1.3
apq8096-tflite 2.8.3-1
libapq8096-io 0.6.0
libmodal-cv 0.2.3
libmodal-exposure 0.0.7
libmodal-journal 0.2.1
libmodal-json 0.4.3
libmodal-pipe 2.6.0
libvoxl-cci-direct 0.1.5
libvoxl-cutils 0.1.1
voxl-camera-calibration 0.2.3
voxl-camera-server 1.3.5
voxl-cpu-monitor 0.3.0
voxl-docker-support 1.2.4
voxl-gphoto2-server 0.0.10
voxl-jpeg-turbo 2.1.3-4
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.3.4
voxl-mavlink 0.1.0
voxl-mavlink-server 0.2.0
voxl-modem 0.16.1
voxl-mongoose 7.7.0-1
voxl-mpa-to-ros 0.3.6
voxl-mpa-tools 0.7.6
voxl-opencv 4.5.5-1
voxl-portal 0.4.2
voxl-qvio-server 0.8.2
voxl-streamer 0.4.1
voxl-suite 0.9.4
voxl-system-image 4.0-r0
voxl-tag-detector 0.0.4
voxl-tflite-server 0.3.1
voxl-utils 1.2.2
voxl-uvc-server 0.1.3
voxl-vision-px4 1.4.0
voxl-vpn 0.0.6

voxl:/$

[José Quintanilla]

@tom I think I need to use the command with the .sh, I'm following this guide https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-python

and the command you want me to do is referring to this guide: https://docs.modalai.com/docker-on-voxl/

[tom]

@José-Quintanilla Its the exact same command, the name was just slightly changed since that page was written.

[José Quintanilla]

@tom Ohh, well thanks, I didn't knew that, thank you

[amitga]

Just to add to this post: I had similar problems with platform image 3.8 (clean install + wipe).
Deleting the /data/network/files didn't help.

I noticed in the systemctl status docker-daemon that there is were various network related errors, probably in the absense of a valid internet connection (VOXL was configured as AP).
For example: Error getting v2 registry: Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid" and "HTTP Error" err="No such image: hello-world:latest" statusCode=404.

After connecting the VOXL to a Wifi router with internet access and rebooting, it seems like the daemon is able to run on boot without issues.

Is this how its supposed to work? Can't a new VOXL install be successful without internet connection ?

Thanks