-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat: RAI dockerfiles #377
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the rationale for having two dockerfiles? I think that a better solution would be to use ARG ROS_DISTRO=jazzy
(for default value). That would halve the need for maintanence of the docker (change one file instead of to) and allow for building with a single parametrized command: docker build --build-arg ROS_DISTRO=humble .
Also I believe it would be a good practice to verify in the CI that the docker images do in fact build, as means of testing. It is a decently common occurance for a docker image to break unexpectedly, so it's good to have that test.
@rachwalk thank you for the feedback. I've refactored dockerfiles into single file and used osrf base image. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maciejmajek Thank you! Good initiative to add docker support.
For clean repo docker seem to work fine with suggested changes, but I failed to build a repo with O3DE examples (I tried with manipulation demo - it lacks moveit
dependencies). I'll report back with a proposal to improve current setup.
@boczekbartek I think the demos define theirs additional deps? |
@maciejmajek Yes, they do. Do you plan to handle them in this PR or should it be implemented in demos? |
@boczekbartek For now, I think that it should be developer's responsibility to install additional dependencies. I'm open to discussing it in the future. I will create an issue regarding docker difficulties in rai |
@maciejmajek Fine by me! I think submitting an issue is a good idea, because demos might need some work to be available through docker. I had some success, but also some problems. Success:
Problems:
error
|
Co-authored-by: Bartek Boczek <[email protected]>
c908b8f
to
093ea39
Compare
Purpose
As discussed in #345, integrating RAI into other environments can be challenging, especially when working with pre-established local setups (e.g., conda installations, custom Python wrappers, etc.). Providing Docker images and Dockerfiles accessible to developers could significantly simplify the process of setting up and using RAI.
Proposed Changes
Introduce experimental Docker images to facilitate easier RAI setup.
Issues
Closing #376
Testing