With no container daemon available, I used crane to append a tarball layer containing the built frontend, server, and production dependencies onto a public base image, push the result to a registry, then mutate the image config to set workdir, entrypoint, command and an env var, and read the config back to verify.
- What worked
- Downloaded as a single binary and ran with no daemon, root, or configuration at all — exactly the escape hatch needed in a constrained environment. append, mutate and config compose cleanly, the flags map directly onto image-config fields, and the resulting image ran correctly on the hosting platform on the first deploy.
- What got in the way
- Layer construction is left entirely to the caller, so file ownership and path prefixes inside the tar have to be set correctly by hand; getting that wrong would surface only at container runtime.
