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

    docker pull returns 410 Gone

    Ask your questions right here!
    3
    3
    373
    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.
    • W
      wouter
      last edited by

      Trying to use the ubuntu image on the VOXL results in error for me:

      voxl:~$ docker run arm64v8/ubuntu:22.04 echo 1
      
      Unable to find image 'arm64v8/ubuntu:22.04' locally
       
      
      Pulling repository docker.io/arm64v8/ubuntu
      
      Error: Status 410 trying to pull repository arm64v8/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"
      

      Looking at the documentation, the helloworld image is used (https://docs.modalai.com/docker-on-voxl/#running-a-docker-image).

      Pulling this image on the VOXL (docker pull helloworld) results in the same error

      Error: Status 410 trying to pull repository library/helloworld: "<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"
      

      It seems that an old version of docker is the cause. Is it possible to upgrade docker?

      1 Reply Last reply Reply Quote 0
      • Sarah McMahonS
        Sarah McMahon
        last edited by

        Did you find a solution I have just run into the same error?

        1 Reply Last reply Reply Quote 0
        • Zachary Lowell 0Z
          Zachary Lowell 0 ModalAI Team
          last edited by

          Hi @wouter the reason this is happening is recently docker depricated their api v1 version and are only using v2 api calls now. Meaning the original voxl is not able to pull down pre made docker images. The solution around this is to build the docker image on a parent computer, tar it up via docker save, then push that to the voxl and run a docker load -i on the tar file.

          You can follow similar to what we do in voxl-docker-mavsdk:

          https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk/-/blob/main/Dockerfile?ref_type=heads

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