Bundle container metadata for future bootable-container support #3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Idea
When building from an OCI image (
build --from-image), save the container metadata (tags, env vars, entrypoint, cmd, working dir, user, etc.) toetc/residual/os/from-docker.jsonin the rootfs.The OCI image config already contains all of this as JSON. We get it for free during the skopeo pull — just save it instead of discarding it.
Future use
Later,
residual-initcan readetc/residual/os/from-docker.jsonand start the container's entrypoint as a managed service. This is a step toward making arbitrary Docker containers fully bootable — the container's entrypoint becomes the system workload, with env vars and config preserved from the original image.Scope
build --from-image, extract OCI image configetc/residual/os/from-docker.jsonin the rootfsNot in scope: the actual
residual-initservice integration (separate issue, later).Hypothetical feature for later. Not blocking current work.