NVIDIA-ISAAC-ROS / NVIDIA-ISAAC-ROS/isaac_ros_common

docker directory error when `Running isaac_ros_dev-aarch64-container `

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

Nobody has claimed this yet.

Dominant language
C++
Stars
317
Forks
227
PR merge metrics
No merged PRs in 30d

Description

I'm trying to launch the Docker container following the Isaac ROS RealSense Setup instructions
Device: Jetson Orin NX 16GB
nv_tegra_release: R36 (release), REVISION: 4.3, GCID: 38968081, BOARD: generic, EABI: aarch64

running run_dev.sh -d ${ISAAC_ROS_WS}

After
Building /home/jetson/workspaces/isaac_ros-dev/src/isaac_ros_common/scripts/../docker/Dockerfile.realsense as image: isaac_ros_dev-aarch64 with base: ros2_humble-image
...

[+] Building 533.5s (13/13) FINISHED

error arises when Running isaac_ros_dev-aarch64-container

docker: Error response from daemon: create /home/jetson/.Xauthority: " /home/jetson/.Xauthority" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path

It seems that there is a needless space character before the directory.

Many thanks to any reply.

Contributor guide

No contributing guide indexed for this repository

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 with run_dev.sh in the Isaac ROS workspace and the Dockerfile.realsense path shown in the build output, then reproduce the container launch on the listed Jetson setup. Trace the volume argument for /home/jetson/.Xauthority; done means the generated argument contains no leading space and the isaac_ros_dev-aarch64-container starts successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.