I have a really minimal container based on a scratch image. It has one statically linked executable that is run as the entrypoint. I switch to a uid using USER 1000 in the Dockerfile, but this causes fly’s init process to panic.
Docker and Podman will happily run a container without an /etc/passwd file as long as the USER command specified a uid and not a username. I’m not sure how Fly can support this as Fly creates a full VM out of this image, while containers are definitely not VMs.
Can the docs explicitly mention that Fly expects a container image to have a valid /etc/passwd file.
Also if we’re keeping track, this is the second time I’ve stumbled in to a kernel panic!