Note that when Fly mounts a volume for the first time, it does not automatically copy over the contents of what’s already included in the destination directory within the Docker image. I wonder if there’s something special about /root in the Docker image that prevents a volume from mounting over it and effectively erasing it.
I asked for Automatic volume initialization like in Docker last year, but understandably Fly probably has a thousand higher priority things to work on.