@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