4 ms·
It's not mentioned on this page, but these runc containers will also run on Windows[1], which is pretty amazing. Not having to run the Docker daemon will also
by waffle_ss 11y ago
It's not mentioned on this page, but these runc containers will also run on Windows[1], which is pretty amazing.
Not having to run the Docker daemon will also be pretty nice. Currently when I upgrade Docker, all containers have to be restarted on the host due to the daemon dependency. So to maintain uptime with Docker containers currently you better be running your stuff clustered (e.g. via Mesos/Marathon).
Standalone containers was something I felt rkt (alternate container format from CoreOS people) got right, so nice to see it carrying over here through the collaboration.
[1]: https://twitter.com/docker/status/613039532422864896 https://twitter.com/docker/status/613039532422864896
- mmastrac 11y agoIs it spinning VirtualBox up in the background or virtualizing syscalls? That's the interesting question.
- nickstinemates 11y agoNeither, Microsoft is creating the equivalents (and more) in the Windows Kernel in the next version of Windows Server and contributing the api compatibility to runC
- geertj 11y agoThis would for running a Windows container, I assume? Microsoft implementing the Linux system call ABI, now that would be truly amazing. I guess it's possible (FreeBSD does some of this), but I guess this is not that?
- delinka 11y agoJudging by the context here, I'm guessing that they're implementing a virtualization API that's capable of creating VMs which run anything an x86 processor can run.
- nickstinemates 11y agoYes, this is for windows specific workloads. Not the ability to virtualize the Linux ABI in Windows. That's what VMs are for.
- tlrobinson 11y agoJoyent did that for SmartOS with their "Triton" project, which lets you run Docker containers on their (SmartOS) cloud.