-
Notifications
You must be signed in to change notification settings - Fork 59
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
Optimize Dockerfiles #110
Merged
Merged
Optimize Dockerfiles #110
Conversation
This file contains 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
achim-k
approved these changes
Dec 12, 2022
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.
Looks good, thank you!
jhurliman
reviewed
Dec 12, 2022
|
||
# Install rosdep dependencies | ||
RUN . /opt/ros/$ROS_DISTRIBUTION/setup.sh && \ | ||
RUN . /opt/ros/$ROS_DISTRO/setup.sh && \ |
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.
I don't see where $ROS_DISTRO
is being set
EDIT: I'm told $ROS_DISTRO is set in the base image
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I was looking at the source Dockerfile for the
ghcr.io/foxglove/rolling-ros2-bridge
image, and noticed some optimizations that could be made. See commit history for details.The only major change is swapping the base image for the ros2 bridge from
ros-core
over toros-base
:I did this as most of the large dependencies being manually installed should already be provided by the base tag. While the resulting image is a little larger
(1.03GB-945MB)=85MB
, the resulting size of the added layers to be regularly pushed over the network and saved to disk with every update to the bridge image is reduced from(945MB-474MB)=471MB
to just(1.03GB-752MB)=278MB
. Given 1) most robots using docker are more likely to have at least the image layers for theros-base
tag cached locally already for other running ROS containers, 2) the lower cadence of changed layers in theros-base
image, this should help reduce the bandwidth and storage requirements for deploying these bridge images.