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
When we run a container based on this image, everything works fine as long as it’s connected to a display and a user is logged in. However, when accessing the container via SSH, GPU access is problematic. Specifically:
A non-root user with the same permissions as the user outside the container cannot access the GPU.
GPU access works when logged in as root.
We also tested the same setup with JetPack 5.1, and this issue does not occur in that version.
If anyone has insights or suggestions on resolving this, please let me know!
Thanks,
Kabir Kedia
The text was updated successfully, but these errors were encountered:
Thanks @kabirkedia , admittedly have not seen this ... is the non-root user part of docker group ? Does --privileged change the behavior? I'm not sure it is the containers themselves rather than a change in the docker daemon?
Thanks for the response, @dusty-nv ! It seems the issue was related to the Docker daemon itself. Although we tried using the --privileged flag, the problem persisted.
We eventually resolved it by enabling automatic login in the Ubuntu GUI. Once that was configured, we were able to access the GPU inside the Docker container successfully.
Interestingly, this issue doesn’t occur with JetPack 35.x, which runs Ubuntu 20.04.
Hello dusty,
Happy New Year! I’m reaching out for help with an issue we’ve encountered while using the official NVIDIA JetPack 6.1 image. Here's the image we’re using: [NVIDIA JetPack 6.1 - PyTorch](https://hub.docker.com/layers/dustynv/l4t-pytorch/r36.4.0/images/sha256-a05c85def9139c21014546451d3baab44052d7cabe854d937f163390bfd5201b).
When we run a container based on this image, everything works fine as long as it’s connected to a display and a user is logged in. However, when accessing the container via SSH, GPU access is problematic. Specifically:
We also tested the same setup with JetPack 5.1, and this issue does not occur in that version.
If anyone has insights or suggestions on resolving this, please let me know!
Thanks,
Kabir Kedia
The text was updated successfully, but these errors were encountered: