ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    mavsdk wont build for voxl2

    Ask your questions right here!
    2
    2
    91
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Gary HolmgrenG
      Gary Holmgren
      last edited by Gary Holmgren

      Hello all, I have been trying to get mavsdk to build for my voxl2 but have not had any luck.

      I keep getting this error when trying to build:

      ~/voxl-docker-mavsdk$ ./build.sh qrb5165
      Image: voxl-mavsdk:v1.2
      Checking for docker support on parent computer to build tar voxl mavsdk
      -> Docker support is running on target. Continuing to build!
      Waiting for voxl device...
      Checking for docker support on modalAI device
      -> Docker support is running on target.
      Building image: voxl-mavsdk:v1.2
      [+] Building 0.5s (2/2) FINISHED                                 docker:default
       => [internal] load build definition from Dockerfile                       0.0s
       => => transferring dockerfile: 1.17kB                                     0.0s
       => ERROR [internal] load metadata for docker.io/arm64v8/ubuntu:focal      0.5s
      ------
       > [internal] load metadata for docker.io/arm64v8/ubuntu:focal:
      ------
      Dockerfile:1
      --------------------
         1 | >>> FROM arm64v8/ubuntu:focal
         2 |     
         3 |     WORKDIR /home
      --------------------
      ERROR: failed to solve: arm64v8/ubuntu:focal: failed to resolve source metadata for docker.io/arm64v8/ubuntu:focal: no match for platform in manifest: not found```
      
      I have followed the README but still haven't figured out whats going on. I am able to build the older mavsdk-python docker just fine however.
      T 1 Reply Last reply Reply Quote 0
      • T
        teddy.zaremba @Gary Holmgren
        last edited by teddy.zaremba

        Hi @Gary-Holmgren. This is likely because you're running the build script from an x86 system (docker requires that you build on the same architecture as the base image, in this case arm64). You can solve that by cloning the repo onto the voxl and running build.sh from there.

        Note: make sure your voxl has a wifi connection before running ./build.sh.

        1 Reply Last reply Reply Quote 1
        • First post
          Last post
        Powered by NodeBB | Contributors