NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_visual_slam
Docker Error - Unknown or Invalid Runtime Name: Nvidia
@hemalshahNV is already working on this.
Since Nov 17, 2023.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
Description
I am encountering a runtime error with Docker when trying to use the Nvidia runtime. This issue arises despite having a successful output with an initial Docker command and making subsequent edits to the Docker configuration.
Steps to Reproduce
-
Run the following Docker command which executes successfully:
sudo docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi -
Edit
/etc/docker/daemon.jsonas follows:{ "runtimes": { "nvidia": { "path": "nvidia-container-runtime", "runtimeArgs": [] } }, "default-runtime": "nvidia" } -
After making these changes, attempt to execute a script with the command:
scripts/run_dev.sh ~/workspaces/isaac_ros-dev/This results in the following error:
docker: Error response from daemon: unknown or invalid runtime name: nvidia.
Expected Behavior
The Docker container should recognize the Nvidia runtime without errors, especially since the initial command runs without issues.
Actual Behavior
The system throws an error stating "unknown or invalid runtime name: nvidia" when trying to run a script that utilizes Docker with the Nvidia runtime.
Environment
- Docker version: Docker version 24.0.7, build afdd53b
- Operating System:ubuntu22.04
- Any other relevant environmental details
Attempts to Resolve
- Verified that the initial Docker command runs successfully.
- Checked the syntax and paths in the
daemon.jsonfile. - Searched for similar issues in forums and GitHub Issues.
Request for Help
Could anyone provide insights or suggest potential solutions to resolve this runtime error? Any advice or guidance would be greatly appreciated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.