Expand description
The Dockerfile Isoloom generates from a container’s recipe (design §2.2–§2.3): FROM its
OS’s official image (pinned by digest), the project folder (/opt/isoloom, the same path a
VM has) as its working folder, then each step in order. Scripts and copies are the
Dockerfile’s own COPY and RUN, a template a COPY of the file Isoloom filled in, and every
other step one RUN of the shell library’s call. A service doesn’t run at build: Isoloom’s
runner (super::runner) is the image’s entrypoint, and starts it. The project folder is the
build context.