Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TASK] Docker Dev Environment on Orin #11

Open
3 tasks
jorgenfj opened this issue Oct 16, 2024 · 2 comments
Open
3 tasks

[TASK] Docker Dev Environment on Orin #11

jorgenfj opened this issue Oct 16, 2024 · 2 comments
Assignees
Labels
devops DevOps team responsible enhancement New feature or request large ~ a couple days to complete perception Perception team responsible

Comments

@jorgenfj
Copy link
Contributor

Description of task

We would like a developer environment for the Orin so we can easily test our code on the required hardware. We have a basic dev-container already set up on the Orin. What remains is tweaking it to our desired use case and integrating our own custom images.

Suggested Workflow

  • The current docker setup was produced by following this Developer Environment Setup. Read through this guide and understand the current setup.
  • The next step is to customize the development environment by following the this on how to customize the environment.

Specifications

  • The config to configure the development environment is placed in the home directory in the provided guide. It is preferred if all docker related configs are embedded within the git repository.
  • We plan to utilize different packages from Isaac Ros v3.1. Since we are dependent on these packages, figure out if we should rely on the dockerfiles and scripts from the isaac_ros_common as our base image / entrypoint. The alternative would be to create own dockerfiles and scripts directly in the perception-auv repo
  • A nice modular design is if each ros package has its own dockerfile to build upon the base image. It would be preferred if the dockerfiles in the submodules for example aruco detection could be launched as standalone containers without relying on the perception-auv repo. Figure out if this is doable with the current setup.

Contacts

@jorgenfj
@Senja20

Code Quality

  • Every function in header files are documented (inputs/returns/exceptions)
  • The project has automated tests that cover MOST of the functions and branches in functions (pytest/gtest)
  • The code is documented on the wiki (provide link)
@VegraD VegraD self-assigned this Oct 16, 2024
@Senja20 Senja20 added devops DevOps team responsible enhancement New feature or request large ~ a couple days to complete perception Perception team responsible labels Oct 16, 2024
@VegraD
Copy link

VegraD commented Oct 16, 2024

create own scrips?! are you crazy??

@VegraD
Copy link

VegraD commented Oct 16, 2024

Should talk to @kluge7 regarding dockerizing ros nodes preferably thursday 17th or sunday 19th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops DevOps team responsible enhancement New feature or request large ~ a couple days to complete perception Perception team responsible
Projects
None yet
Development

No branches or pull requests

3 participants