voxl-docker-mavsdk-python build issues

[Alexander Saunders]

@Eric-Katzfey Just to make sure I'm not misunderstanding you, you want me to the instructions below that is coming from: https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-python!Screenshot 2024-05-22 at 4.39.11 PM.png

[Eric Katzfey]

@Alexander-Saunders Yes

[Alexander Saunders]

@Eric-Katzfey Good morning Eric,

So I tried building the image for both voxl-docker-mavsdk & voxl-docker-mavsdk-python. I run into the same issue with both, adb: command not found. Additionally, with voxl-docker-mavsdk-python the common file is not found.

the ./build-image.sh was run on both directories in both SSH and ADB shell.

I am at a standstill with testing until I can get the docker image built. Any additional documentation is greatly appreciated!

Respectfully,
Alexander

[Eric Katzfey]

@Alexander-Saunders You run build-image.sh on your host computer, not on the voxl

[Alexander Saunders]

@Eric-Katzfey Hey Eric, I'm running the ./build-image.sh on a laptop and am running into this error.

[Alexander Saunders]

@Eric-Katzfey

[Eric Katzfey]

@Alexander-Saunders Oh, the repo probably has the name master changed to main. Can you change the Dockerfile to try to use main instead of master and see if that works?

[Alexander Saunders]

@Eric-Katzfey No luck with that. Also the branch is a master.

[Eric Katzfey]

@Alexander-Saunders But that's a different problem. Before it was the checkout of master. This is something else.

[Eric Katzfey]

@Alexander-Saunders I'll try it and see what happens.

[Eric Katzfey]

@Alexander-Saunders Okay, yes, I see the same error. Sorry about that. Let me see if I can figure out what is going wrong.

[Eric Katzfey]

@Alexander-Saunders Can you try with the origin/ascend/docker branch of voxl-docker-mavsdk-python instead? Seems like that's where the latest updates have happened and haven't been merged back into master yet.

[Alexander Saunders]

@Eric-Katzfey I went ahead and tried the voxl-docker-mavsdk repo also and get the same issue. I tried docker pull docker.io/arm64v8/ubuntu:bionic and giving the user permissions for the file/folder.

What is stumping me is the registry-1.docker.io. I can ping it and do a DNS lookup just fine. Also pinging google is fine. But the error is persisting in relation to it.

I will try the other branches for voxl-docker-mavsdk andvoxl-docker-mavsdk-python. Will that require changing main to the branch name for the DockerFile?

[Alexander Saunders]

@Eric-Katzfey This is from the ascend branch

[Eric Katzfey]

@Alexander-Saunders Not sure why that is happening. That does not happen when I try it. I'm guessing that you have a networking issue of some sort or perhaps all this messing with Docker on the target has somehow corrupted it and it needs to be reinstalled.

[Alexander Saunders]

@Eric-Katzfey So I deleted and re cloned voxl-docker-mavsdk-python branch ascend/docker. The build image failed halfway in. Is there any work that needs to be done on the VOXL2 or host computer that I am not aware of?

[Alexander Saunders]

@Eric-Katzfey Also in the environment, the SDK is 1.2, python 3.10.12, Ubuntu 22.04.4 LTS

[Eric Katzfey]

@Alexander-Saunders Okay, we're looking into it, thanks!

[Alexander Saunders]

@Eric-Katzfey Thank you! What kind of timeline should I expect to hear back from you?

[brahim]

@Alexander-Saunders I am testing a fix for this issue as we speak. I've sourced the problem to a Mavsdk dependency that had a recent upstream change which is causing issues on the voxl2 build image script.