On Sun, 2019-03-31 at 11:54 -0700, Waldek Kozaczuk wrote: > The second group's need should be addressed by Capstan. So we should > avoid duplication between what Capstan does well (and hopefully will > do even better in future) and OSv build system. Now capstan packages > are often generated using osv-apps and OSv build system.
As I've mentioned before - we're using a plugin I wrote to the erlang build tool 'rebar3' which takes an erlang/OTP application and an OSv base image and builts a unikernel image. The reason for this approach is the slightly complex nature of making the image. We're emulating what the OSv build system does, using cpio to push in the components to the file system over a tcp port. Is that what capstan does too? Or is there a simpler way that I've missed? 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
