On 28/04/15 23:33, Andrew Stuart wrote:
You can then bake those files into an image that you present as a disk device
to rumprun.
I had runtime configuration in mind rather than pre-baked. Consider
certificates and keys - I can give you a rumpkernel and if the certs can be
copied onto the disk before launch then the kernel build process never need
access to your certs.
I completely agree that you shouldn't need the data files when you build
the rumprun image.
I was suggesting you'd package your data files at launch-time. That's
essentially what Martin's run-nginx.sh does, even though it builds the
images as part of "make". You could easily make run-nginx.sh build the
images instead, and maybe we'll even add that support to the rumprun
launch tool once we gain some more understanding of the intricacies of
various use cases.
I'm not seeing a conceptual difference between the milliseconds that the
guest is launched and before it bootstraps to the point of calling the
application main. The only thing I can think of is that the guest might
have access to a different network, but I have a hard time guessing why
the host couldn't be configured for access to the same network. So if
there is a conceptual difference, you'll have to explain it more
explicitly so that we can help you better.
