> What I think is a better approach is to take separatey the OSv kernel with > just cpiod.so and mkfs.so (i.e., take build/release/loader.img) and the > files, and compose the image with the size you want and uploading the files > you want to it. This is more-or-less what the Mikelangelo project's fork of > Capstan is doing. Maybe that's what you are also planning to do?
That is indeed the intention. Right now, I’m building an Erlang/OTP with the patches from your modules/ directory and reference that from the rebar build (just as you would if you were cross-compiling an erlang/otp application). The ‘base’ image I’m using is created image with libncurses, ssl etc. Once a few Erlang/OTP build issues are sorted, I may move to using loader.img, but it is convenient to have an image with cloud-init and the httpserver installed too... Cheers, Rick -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
