4 ms·

Wherein the author argues that requiring a single OS kernel for multiple containers is somehow more restrictive than MirageOS, which requires every application

Wherein the author argues that requiring a single OS kernel for multiple containers is somehow more restrictive than MirageOS, which requires every application to be written in OCaml? The overall concept is not without merit, the OSv site (http://osv.io/resources/ http://osv.io/resources/) has some more interesting material. I'll still be sticking with Docker though.

mackwic 12y ago
What's the big deal with OCaml ? I found it to be a very nice, powerful, and enjoyable language.
- dmpk2k 12y ago
  There's nothing wrong with OCaml specifically. The problem is the overall argument, which seems to fundamentally misunderstand why machine virtualisation is used.
- vidarh 12y ago
  "The big deal with OCaml" is that most people have tons of code that isn't written in OCaml. Projects like MirageOS and ErlangOnXen are fantastic and I hope we see more of them, but getting to the point where these kinds of runtimes are viable for most people is a long road.
  - amirmc 12y ago
    They are viable for people starting afresh. Not everything that comes along has to care about legacy systems so the advantage goes to those creating new tools/products/services with the advanced approaches. In fact, I'd argue that such step changes wouldn't be possible if we always had to be compatible. This is pretty much 'circle of life' stuff.
amirmc 12y ago
The point about Mirage (and it's ilk) is that you can retain the benefits of the Hypervisor (security etc), while also gaining the benefits of streamlined deployment. Those who can or choose to use such approaches will benefit from the best of both worlds. In general, I see things like Docker/Mirage/Xen to be complementary, rather than antagonistic. A good example of this is Google's Docker support, which is via a custom VM. https://developers.google.com/compute/docs/containers https://developers.google.com/compute/docs/containers

mackwic 12y ago

What's the big deal with OCaml ? I found it to be a very nice, powerful, and enjoyable language.

dmpk2k 12y ago
There's nothing wrong with OCaml specifically. The problem is the overall argument, which seems to fundamentally misunderstand why machine virtualisation is used.
vidarh 12y ago
"The big deal with OCaml" is that most people have tons of code that isn't written in OCaml. Projects like MirageOS and ErlangOnXen are fantastic and I hope we see more of them, but getting to the point where these kinds of runtimes are viable for most people is a long road.
- amirmc 12y ago
  They are viable for people starting afresh. Not everything that comes along has to care about legacy systems so the advantage goes to those creating new tools/products/services with the advanced approaches. In fact, I'd argue that such step changes wouldn't be possible if we always had to be compatible. This is pretty much 'circle of life' stuff.

amirmc 12y ago

The point about Mirage (and it's ilk) is that you can retain the benefits of the Hypervisor (security etc), while also gaining the benefits of streamlined deployment. Those who can or choose to use such approaches will benefit from the best of both worlds. In general, I see things like Docker/Mirage/Xen to be complementary, rather than antagonistic. A good example of this is Google's Docker support, which is via a custom VM. https://developers.google.com/compute/docs/containers https://developers.google.com/compute/docs/containers