-
Notifications
You must be signed in to change notification settings - Fork 6
Conversation
This pull request has been linked to Shortcut Story #11560: Create Template Dockerfile, .env, and docker-compose.yaml for Tutorials. |
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.
Some minor comments. Most of them are take or leave it since this is almost exactly what we have already delivered to customers.
# hadolint ignore=SC1091 | ||
RUN --mount=type=cache,target=/var/cache/apt,sharing=locked \ | ||
--mount=type=cache,target=/var/lib/apt,sharing=locked \ | ||
. "${OVERLAY_WS}/install/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.
Someday we should get on renaming this.
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.
yeah... overlay is such a loaded word. Giovanni was right all along and we shouldn't have used other ROS repos as precedent lol
Thanks for the comments, @eholum -- I implemented them all! |
* Update config packages and example Behaviors * Add overlay Docker image option (#1) Co-authored-by: Michael Wrock <Michael Wrock> Co-authored-by: Sebastian Castro <[email protected]>
This partially addresses [sc-11560] by adding the option for users to build their own release / dev images on top of our binaries containers for Studio.
In these cases, there would be no notion of a "user workspace" as it's all contained within the image (treated the same way the overlay workspace would in core Studio).
I say "partially addresses" because the tutorial portion of this needs to happen in our actual docs.