You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
like this: docker pull nvidia/cuda:11.8.0-devel-ubuntu22.04
After the successful download, I am trying to run the image like this: docker run nvidia/cuda:11.8.0-devel-ubuntu22.04
But it is giving me the following error:
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v2.task/moby/305e31cc5a8870eba58fd1433edd6dffca4b66c86f2d00997a1e847abbad76f2/log.json: no such file or directory): fork/exec /usr/bin/nvidia-container-runtime: no such file or directory: unknown.
ERRO[0001] error waiting for container: context canceled
Now, I don't have nvidia drivers or nvidia container toolkit installed on this VM and I see that to be the reason why. However, when I do install the drivers with sudo ubuntu-drivers autoinstall and sudo apt-get install nvidia-container-toolki, I get version mismatch.
Where am I going wrong?
The text was updated successfully, but these errors were encountered:
Hi.
I pull this image: https://hub.docker.com/layers/nvidia/cuda/11.8.0-devel-ubuntu22.04/images/sha256-0c4830108130fe92fa3e9ba8a9a813bf1264e2cddd1902b2c30750aada5ede38?context=explore
like this: docker pull nvidia/cuda:11.8.0-devel-ubuntu22.04
After the successful download, I am trying to run the image like this: docker run nvidia/cuda:11.8.0-devel-ubuntu22.04
But it is giving me the following error:
Now, I don't have nvidia drivers or nvidia container toolkit installed on this VM and I see that to be the reason why. However, when I do install the drivers with
sudo ubuntu-drivers autoinstall
andsudo apt-get install nvidia-container-toolki
, I get version mismatch.Where am I going wrong?
The text was updated successfully, but these errors were encountered: