NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_object_detection

./scripts/run_dev.sh

Open
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
201
Forks
51
PR merge metrics
No merged PRs in 30d

Description

Hello, when I follow the documentation https://nvidia-isaac-ros.github.io/repositories_and_packages/isaac_ros_object_detection/isaac_ros_rtdetr/index.html to Build isaac_ros_rtdetr, I get the following error which I have not been able to resolve.The following is the error message:

ubuntu@hjj:~/workspaces/isaac_ros-dev/src/isaac_ros_common$ ./scripts/run_dev.sh
Error: failed to call git rev-parse --git-dir: exit status 128 : fatal: 不是 git 仓库(或者任何父目录):.git

Launching Isaac ROS Dev container with image key x86_64.ros2_humble.realsense.user: /home/ubuntu/workspaces/isaac_ros-dev/
Building x86_64.ros2_humble.realsense.user base as image: isaac_ros_dev-x86_64
Building layered image for key x86_64.ros2_humble.realsense.user as isaac_ros_dev-x86_64
Using configured docker search paths: /home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker
Checking if base image nvcr.io/isaac/ros:x86_64-ros2_humble-realsense-user_049ad2f527c049d6b00773df2572776e exists on remote registry
Checking if base image nvcr.io/isaac/ros:x86_64-ros2_humble-realsense_31d1e3814d2f05cabf13a02a9a5615d4 exists on remote registry
Checking if base image nvcr.io/isaac/ros:x86_64-ros2_humble_c1c0329fbb38334201e8550c18d58b1a exists on remote registry
Checking if base image nvcr.io/isaac/ros:x86_64_4ed3433cd93546ce1af666f189f5dfeb exists on remote registry
Resolved the following 4 Dockerfiles for target image: x86_64.ros2_humble.realsense.user
/home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.user
/home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.realsense
/home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.ros2_humble
/home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.x86_64
Building /home/ubuntu/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.x86_64 as image: x86_64-image with base:
[+] Building 1.1s (2/2) FINISHED docker:default
=> [internal] load build definition from Dockerfile.x86_64 0.0s
=> => transferring dockerfile: 5.98kB 0.0s
=> ERROR [internal] load metadata for nvcr.io/nvidia/tritonserver:23.10-py3 1.0s

[internal] load metadata for nvcr.io/nvidia/tritonserver:23.10-py3:


Dockerfile.x86_64:13

11 | # https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html
12 | ARG BASE_IMAGE=nvcr.io/nvidia/tritonserver:23.10-py3
13 | >>> FROM ${BASE_IMAGE}
14 |
15 | # Store list of packages (must be first)

ERROR: failed to solve: nvcr.io/nvidia/tritonserver:23.10-py3: failed to resolve source metadata for nvcr.io/nvidia/tritonserver:23.10-py3: unexpected status from HEAD request to https://nvcr.io/v2/nvidia/tritonserver/manifests/23.10-py3: 403 Forbidden
~/workspaces/isaac_ros-dev/src/isaac_ros_common

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing ./scripts/run_dev.sh from the reported workspace and inspect scripts/run_dev.sh and docker/Dockerfile.x86_64, including the nvcr.io/nvidia/tritonserver:23.10-py3 base image. Determine whether the 403 registry response has a repository-level resolution; done should be a documented or validated way to complete the build.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
build-system, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.