Mirage – A programming framework for building type-safe, modular systems
1–10 of 92 posts
Re: Mirage – A programming framework for building type-safe, modular systems
#2Also with a bit living inside Docker.
Re: Mirage – A programming framework for building type-safe, modular systems
#3The FAQ mentions that this can run in QEMU. Are there cloud providers that support hosting a custom ISO? I feel like that would be hard to secure.
Re: Mirage – A programming framework for building type-safe, modular systems
#4The FAQ mentions that this can run in QEMU. Are there cloud providers that support hosting a custom ISO? I feel like that would be hard to secure.
Lots of them. VPS typically are not secured at the os level, but as separate VMs. For the cloud provider it's just a matter of picking an ISO (plus a few management extensions but those are usually optional)
Re: Mirage – A programming framework for building type-safe, modular systems
#5The FAQ mentions that this can run in QEMU. Are there cloud providers that support hosting a custom ISO? I feel like that would be hard to secure.
Lots of them. VPS typically are not secured at the os level, but as separate VMs. For the cloud provider it's just a matter of picking an ISO (plus a few management extensions but those are usually optional)
Digitalocean supports it: https://docs.digitalocean.com/glossary/iso-image/
Re: Mirage – A programming framework for building type-safe, modular systems
#6I'm intrigued but your site gives me little to go on, I feel like I'm missing a big "what this is" page
Re: Mirage – A programming framework for building type-safe, modular systems
#7Is that similar to Firecracker?
Re: Mirage – A programming framework for building type-safe, modular systems
#8I'm really sold on the idea: Instead of a full-blown OS, you compile your application with a thin layer of support libraries that provide the OS features that your application needs (network, I/O) and that talks to a hypervisor.
I mean, if your application runs in a virtualized environment, there's little need to SSH into the system in the first place (except for debugging purposes). Thus, why bother with a full-blown operating system? In the virtualized case, the true OS logic is in the host OS anyway, talking to the hardware. Cutting out all those superfluous layers in the app VM makes it small, start quickly, and gives less attack surface. Sounds like a win-win to me.
In contrast, FreeBSD on Firecracker is a full-blown OS, but boots in 25 milliseconds on the Firecracker hypervisor.
Re: Mirage – A programming framework for building type-safe, modular systems
#9I'm really sold on the idea: Instead of a full-blown OS, you compile your application with a thin layer of support libraries that provide the OS features that your application needs (network, I/O) and that talks to a hypervisor. I mean, if your application runs in a virtualized environment, there's little need to SSH into the system in the first place (except for debugging purposes). Thus, why bother with a full-blow…
Isn’t that the aim of webassembly?
Re: Mirage – A programming framework for building type-safe, modular systems
#10I'm really sold on the idea: Instead of a full-blown OS, you compile your application with a thin layer of support libraries that provide the OS features that your application needs (network, I/O) and that talks to a hypervisor. I mean, if your application runs in a virtualized environment, there's little need to SSH into the system in the first place (except for debugging purposes). Thus, why bother with a full-blow…
Isn’t this the same idea behind unikernels?