Xilinx / Vitis-AI-Tutorials

MIT License
400 stars 146 forks source link

Issue in lauching the docker image #110

Open yashg1905 opened 1 year ago

yashg1905 commented 1 year ago

I am facing this error while launching the docker images Error response from daemon: pull access denied for xilinx/vitis-ai-tensorflow2-gpu, repository does not exist or may require 'docker login': denied: requested access to the resource is denied docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].

BusyBeeATais commented 1 year ago

Hi, the gpu images are not public. But you can build the GPU image yourself in the vitis repo. The images for Vitis-AI 3.5 and 3.0 work. For the versions 2.0 and 2.5 you have to modify the base image. Here is a link to docker_build.sh https://github.com/Xilinx/Vitis-AI/tree/master/docker

To the GPU thematics, there you have to install the appropriate CUDA driver. Here is a link to the installation you need: https://xilinx.github.io/Vitis-AI/3.5/html/docs/install/install.html (Here is also something about the docker build script)

If you don't have an Ubuntu 20.04 system as host you can build one with wsl and gpu pass trough. Here is a tutorial: https://medium.com/htc-research-engineering-blog/nvidia-docker-on-wsl2-f891dfe34ab

Use Windows Terminal and ubuntu 20.04 to use the tools. Found a complete Tutorial on this issue: https://def-var.net/project/kira-kv260-part-ii-vitis-ai-workflow-on-windows-with-wsl-and-gpu-pass-through/

dvdsosa commented 2 months ago

I am facing this error while launching the docker images Error response from daemon: pull access denied for xilinx/vitis-ai-tensorflow2-gpu, repository does not exist or may require 'docker login': denied: requested access to the resource is denied docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].

I had your same error in Ubuntu 24.04LTS, and I solved it by first, re-installing docker as stated here by the user 262926outiuka03 (Member) and then installing the NVIDIA Container Toolkit as explained here to solve your reported issue.

Cheers! David.