Many developers want to understand how to enable the reuse of an existing container image each time a session is started, as opposed to rebuilding the container from scratch so that:
- Create a codified build event for deterministic environment definition
- Speed environment creation
- In the Codespaces Prebuilds case, work around the limitation that Codespaces do not follow a fork by
We documentation prebuilding dev container images, but none of our templates illustrate good practices for this, and the documentation is a but buried.
I propose that we create a guide that describes how to decide if you need to prebuild, walk through the mechanics on GitHub with Actions and GHCR, and provides a few good examples.
It would also help if we update the templates where a prebuilt image would help to illustrate the pattern.
Many developers want to understand how to enable the reuse of an existing container image each time a session is started, as opposed to rebuilding the container from scratch so that:
We documentation prebuilding dev container images, but none of our templates illustrate good practices for this, and the documentation is a but buried.
I propose that we create a guide that describes how to decide if you need to prebuild, walk through the mechanics on GitHub with Actions and GHCR, and provides a few good examples.
It would also help if we update the templates where a prebuilt image would help to illustrate the pattern.