docker.dev environment for desktop development#511
Open
eminmeydanoglu wants to merge 9 commits intomainfrom
Open
docker.dev environment for desktop development#511eminmeydanoglu wants to merge 9 commits intomainfrom
eminmeydanoglu wants to merge 9 commits intomainfrom
Conversation
eminmeydanoglu
changed the title
Removed the depth_anything_node configuration from the launch file.
Removed depth_anything_client.py from CMakeLists.txt.
Collaborator
Author
|
Lets merge 🗡️ |
Member
|
How about adding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a complete local development setup for simulation work. I needed something different from our existing Docker images.
Why did you not use the existing images?
Our CI builds Dockerfile.auv and Dockerfile.auv-base for production. These are headless. no GUI - RViz - Gazebo window. They use ros:noetic-ros-base because we don't need visualization on Jetson or in CI pipelines.
How?
The docker environment for development is intended to include everything a native ubuntu setup does. Container is mounted to auv_software at host. This enables live read-write, just as a native setup.
Use:
Run ./run.sh from the docker folder. First run builds the base image (~10 minutes). After that, builds take about a minute because dependencies are cached.
cd docker ./run.shThe script creates the container and drops you into Zsh. Your code is mounted live. edit on host, changes appear instantly in container. No rebuild needed for code changes.
To stop, just exit the shell. The container keeps running. Next time you run ./run.sh, it reconnects to the existing container. All your installed packages and terminal history persist.
To fully reset, use docker compose down (generally not needed - this is like formatting your computer. Instead use docker stop)