Unable to Generate the Mavsdk Docker on a M500
-
Hello,
I’ve recently started working with the Modal AI M500 drone and am encountering issues while trying to build Docker images on the drone. Specifically, I am having trouble with both the Mavsdk and Mavsdk-Python images.
Issue 1: Pulling Docker Image
When attempting to pull the Python Docker image (
modalai-public/voxl-mavsdk-python), I receive the following error:Error: Status 405 trying to pull repository modalai-public/voxl-mavsdk-python: "v1 Registry API is disabled. If you are not explicitly using the v1 Registry API, it is possible your v2 image could not be found. Verify that your image is available, or retry with `dockerd --disable-legacy-registry`. See https://cloud.google.com/container-registry/docs/support/deprecation-notices"Issue 2: Building Docker Image on Drone
I also tried building the Docker image directly on my computer while connected to the drone via ADB, but encountered this error:
Image: voxl-mavsdk-python:v1.1 Waiting for device... Checking for docker support... -> Docker support not detected, running docker support on target... /bin/sh: voxl-configure-docker-support.sh: not found Building image: voxl-mavsdk-python:v1.1 Dockerfile: 1 file pushed. 0.3 MB/s (802 bytes in 0.002s) takeoff_and_land2.py: 1 file pushed. 0.4 MB/s (941 bytes in 0.002s) offboard_position_ned2.py: 1 file pushed. 0.8 MB/s (2227 bytes in 0.003s) start-mavsdk-server.sh: 1 file pushed. 0.0 MB/s (109 bytes in 0.007s) Sending build context to Docker daemon 8.192 kB Step 1 : FROM ubuntu:22.04 Pulling repository docker.io/library/ubuntu Error: Status 410 trying to pull repository library/ubuntu: "<html>\r\n<head><title>410 Gone</title></head>\r\n<body>\r\n<center><h1>410 Gone</h1></center>\r\n<hr><center>openresty</center>\r\n</body>\r\n</html>\r\n"Additional Information
- Docker Version: 1.9.0 on the VOXL
- Drone Firmware Version: - I just updated it to the newest SDK version 1.2.
Could someone please assist me with these issues? Any guidance or suggestions would be greatly appreciated.
Thank you!
-
@Sarah-McMahon Hi! So it appears that as of this month Docker actually fully depracated their V1 API registry meaning that leveraging docker pull to pull down an already made docker image from dockerhub results in a 410 error (This is only an issue on the voxl1 as the docker instance is quite old and yocto doesn't play nice with the newer versions of docker). We are currently developing a quick fix that can build the voxl-docker-mavsdk image on a parent computer and then push that to the voxl1 on the m500 to leverage. Should hopefully have something in the next few days.
Thanks!
-
@Sarah-McMahon please clone down most recent main:
https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk
Then follow the build instructions to build the voxl-docker-mavsdk docker instance and then push it to the voxl to load and run there. LMK if you run into any issues!
-
@Zachary-Lowell-0 I encountered an issue with the threading during the download process, which caused it to take about 9 hours. The main problem arose when running deploy-to-voxl.sh—the drone ran out of storage after pushing the tar file, preventing the image from being loaded into Docker. While attempting to free up space, I mistakenly ran the wrong opkg command and deleted all opkg packages, making it impossible to SSH or ADB into the drone. Do you have any suggestions for a potential fix? I noticed the USB Expander and Debug Add-On Board might be helpful, but I couldn't find it available for purchase on the website.
-
@Sarah-McMahon said in Unable to Generate the Mavsdk Docker on a M500:
@Zachary-Lowell-0 I encountered an issue with the threading during the download process, which caused it to take about 9 hours. The main problem arose when running deploy-to-voxl.sh—the drone ran out of storage after pushing the tar file, preventing the image from being loaded into Docker. While attempting to free up space, I mistakenly ran the wrong opkg command and deleted all opkg packages, making it impossible to SSH or ADB into the drone. Do you have any suggestions for a potential fix? I noticed the USB Expander and Debug Add-On Board might be helpful, but I couldn't find it available for purchase on the website.
Reply
Hi Sarah - I am unsure if I am following - the docker tarball is only a few gig's so I am unsure how you ran out of space. For now I would just reflash your voxl from the downloads page here https://developer.modalai.com/categories (download the most recent voxl1 sdk unzip it and run the install script from the parent computer) - this will reinstall the entire sys image and newest SDK onto the voxl and allow you to adb shell and ssh in again. From there you will need to configure the SKU and mpa and then you can try the docker installation again from the parent computer.
Can you let me know how big your image is for the mavsdk docker tarball? And if you run df -h on your voxl can you paste the output I want to see where all your disk space is being utilized.
Zach
