voxl-docker-mavsdk-python build issues
-
@Alexander-Saunders , I am not sure about this one, i asked my colleague to check it out.
Alex
@Alex-Kushleyev Good afternoon,
I'm just following up with you to see if there an update with the process of enabling MAVSDK with the VOXL2.
I did some research on my end and am getting conflicting information on what is necessary for the older VOXL and the VOXL2.
In the section relating to VOXL2: https://docs.modalai.com/docker-on-voxl/#download--push-a-docker-image-to-voxl, voxl-configure-docker-support.sh is not recommended to be ran, but for the README from the link on MAVSDK on VOXL2, I'm told to run said command.
I am aware the link above is in reference to Ubuntu, but the command is shared between VOXL and VOXL2 documentation.
Also the location /data/docker/mavsdk does not exist that is referenced in the documentation, but /data directory does.
Could you or someone else follow up with me on which parts of the documentation is for VOXL or VOXL2 so that I can pull down the docker image for MAVSDK. If just enabling the parameters and running the services for voxl-vision-hub and voxl-mavlink-server is all or going through the normal Docker install on VOXL2, can you share that.
Thank you,
Alexander
-
@Alex-Kushleyev Good afternoon,
I'm just following up with you to see if there an update with the process of enabling MAVSDK with the VOXL2.
I did some research on my end and am getting conflicting information on what is necessary for the older VOXL and the VOXL2.
In the section relating to VOXL2: https://docs.modalai.com/docker-on-voxl/#download--push-a-docker-image-to-voxl, voxl-configure-docker-support.sh is not recommended to be ran, but for the README from the link on MAVSDK on VOXL2, I'm told to run said command.
I am aware the link above is in reference to Ubuntu, but the command is shared between VOXL and VOXL2 documentation.
Also the location /data/docker/mavsdk does not exist that is referenced in the documentation, but /data directory does.
Could you or someone else follow up with me on which parts of the documentation is for VOXL or VOXL2 so that I can pull down the docker image for MAVSDK. If just enabling the parameters and running the services for voxl-vision-hub and voxl-mavlink-server is all or going through the normal Docker install on VOXL2, can you share that.
Thank you,
Alexander @Alexander-Saunders VOXL has Docker pre-installed but you need to run voxl-configure-docker-support.sh in order to enable it. VOXL 2 does not have Docker pre-installed, but since it is a Debian-based platform you can just install Docker the standard way. For VOXL 2 you do not use voxl-configure-docker-support.sh.
-
@Alex-Kushleyev Good afternoon,
I'm just following up with you to see if there an update with the process of enabling MAVSDK with the VOXL2.
I did some research on my end and am getting conflicting information on what is necessary for the older VOXL and the VOXL2.
In the section relating to VOXL2: https://docs.modalai.com/docker-on-voxl/#download--push-a-docker-image-to-voxl, voxl-configure-docker-support.sh is not recommended to be ran, but for the README from the link on MAVSDK on VOXL2, I'm told to run said command.
I am aware the link above is in reference to Ubuntu, but the command is shared between VOXL and VOXL2 documentation.
Also the location /data/docker/mavsdk does not exist that is referenced in the documentation, but /data directory does.
Could you or someone else follow up with me on which parts of the documentation is for VOXL or VOXL2 so that I can pull down the docker image for MAVSDK. If just enabling the parameters and running the services for voxl-vision-hub and voxl-mavlink-server is all or going through the normal Docker install on VOXL2, can you share that.
Thank you,
Alexander @Alexander-Saunders You should try building the Docker container instead of downloading it from the repo since that seems to not be functional at the moment (Looking into it).
-
@Alexander-Saunders You should try building the Docker container instead of downloading it from the repo since that seems to not be functional at the moment (Looking into it).
This post is deleted! -
@Alexander-Saunders You should try building the Docker container instead of downloading it from the repo since that seems to not be functional at the moment (Looking into it).
@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 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 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 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 @Alexander-Saunders You run build-image.sh on your host computer, not on the voxl
-
@Alexander-Saunders You run build-image.sh on your host computer, not on the voxl
@Eric-Katzfey Hey Eric, I'm running the ./build-image.sh on a laptop and am running into this error.
-
@Alexander-Saunders You run build-image.sh on your host computer, not on the voxl
-
@Eric-Katzfey Hey Eric, I'm running the ./build-image.sh on a laptop and am running into this error.
@Alexander-Saunders Oh, the repo probably has the name
masterchanged tomain. Can you change the Dockerfile to try to use main instead of master and see if that works? -
@Alexander-Saunders Oh, the repo probably has the name
masterchanged tomain. Can you change the Dockerfile to try to use main instead of master and see if that works?@Eric-Katzfey No luck with that. Also the branch is a master.
-
@Eric-Katzfey No luck with that. Also the branch is a master.
@Alexander-Saunders But that's a different problem. Before it was the checkout of master. This is something else.
-
@Eric-Katzfey No luck with that. Also the branch is a master.
@Alexander-Saunders I'll try it and see what happens.
-
@Eric-Katzfey No luck with that. Also the branch is a master.
@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 No luck with that. Also the branch is a master.
@Alexander-Saunders Can you try with the
origin/ascend/dockerbranch 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 But that's a different problem. Before it was the checkout of master. This is something else.
@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 Can you try with the
origin/ascend/dockerbranch 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.@Eric-Katzfey
This is from the ascend branch -
@Eric-Katzfey
This is from the ascend branch@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 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.
@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?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login