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

work with docker

Open
#157 1 comment 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

Good afternoon
I tried to run run-dev.sh when docker was running in ROOTLESS mode, it worked poorly - the topics inside docker were not visible, also when calling, for example, realsense-viewer there was no image on the screen, errors like 'I CANNOT find the display))'.

After a week of torment) I turned off ROOTLESS mode:

  1. systemctl --user disable docker.service
  2. sudo systemctl enable docker.service
  3. sudo systemctl enable docker.socket
  4. sudo usermod -aG docker username # to run docker without typing 'sudo' in front
    , and everything worked )))))) topics appeared and output appeared on the screen

But the question is different, since now I believe that issac ros works))), how can I save the container configuration after running run-dev.sh and after installing additional packages. I ran 'docker commit ... ' from the second term while the container created by run-dev.sh was running? but after the next launch of the saved container, the data from workspases/issac_ro_dev/ .... and the lower subfolders were not visible. What is the best way to do this?

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 and the Docker invocation it uses, then inspect how workspaces/issac_ro_dev/ is mounted or recreated. Reproduce the container launch and docker commit workflow, and document the supported way to preserve installed packages and workspace data across launches, including the rootless-mode limitations described here.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, tooling
Issue type
Documentation
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.