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

Using Docker-compose to Manage Docker Lifecycle

Open
#113 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 am using an NVIDIA Orin with a 5.1.2 Jeptack. I am running ros2 nodes through docker from run_dev.sh which works fine. Each docker session is responsible for one task (for example: navigation), with the hopes that the process is isolated.

For further development, I wanted to manage the docker lifecycle and thought that docker-compose would be a good solution for it. My issue is that the way we launch docker by default through run_dev.sh which sets a lot of stuff to make sure the docker is robust and set-up properly is complicated to incorporate it within the docker-compose yaml.

I installed docker-compose and tried "docker-compose build" on Dockerfile.aarch64.ros2_humble which I believe is the base of the ROS2, and the container works fine. But it fails when I tried to launch docker-compose on Dockerfile.user. The error states that it is unable to find user admin, which I believe is a job that the build_base_image.sh would do in the default setup through run_dev.sh.

Regarding the direction of what I am doing, is this correct? or can somebody point-out me the correct way how people would manage the lifecycle of containers? or probably a guide?

The sole guide that I found is from seabrass which covers the usage of ROS2 and docker compose. Thank you.

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

Review run_dev.sh, build_base_image.sh, Dockerfile.aarch64.ros2_humble, and Dockerfile.user to map the current setup and the admin-user failure. Compare that flow with the requested Docker Compose lifecycle guidance; the issue does not define a specific documentation change or a clear completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, shell
Domain
devops, infrastructure, robotics
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.