3 ms·
My understanding from talking to people working on MirageOS is that a lot of the unikernel users are still deploying inside containers. Just like containers are
by jzelinskie 11y ago
My understanding from talking to people working on MirageOS is that a lot of the unikernel users are still deploying inside containers. Just like containers aren't going to "kill" virtualization, unikernels aren't going to "kill" containers.
I'd particularly like to stress the part of the article that mentions containers that bring all of userland with them. I hope this will be fixed once people are using tools like Kubernetes and are forced to think of containers as pieces of a larger system rather than short-sightedly "porting" their applications into a container. At CoreOS, we introduced Clair[0] specifically to show people how much userland is still inside their containers and vulnernable to known CVEs. ~80% of tags (downloadable containers) on Quay.io still contain Heartbleed, for crying out loud.
[0]: https://github.com/coreos/clair https://github.com/coreos/clair
- jacques_chester 11y ago> I hope this will be fixed once people are using tools like Kubernetes and are forced to think of containers as pieces of a larger system rather than short-sightedly "porting" their applications into a container. Could you elaborate a bit? I don't see how the scheduler changes the contents of a container image.
- Gigablah 11y agoI think it's more of people treating their containers like VMs and stuffing it with things like sshd, syslog, a webserver, etc.