Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why make bootable images, as opposed to docker images? What sorts of applications do you see using this?


Hardware level isolation. Or: if you run your docker container as a vm instance; reduced overhead with only the kernel parts you need.

Typical docker is just a glorified chroot under a shared Linux kernel. With namespaces it asymptotically approach a bsd jail.

But the "easy" way to get some real isolation, is to use hw support for virtualization - but now you need a kernel (software that enable programs to talk via a fixed abstraction to hardware; drivers for real and emulated hw).

And you've reinvented 5% of the magic dust that IBM put into mainframes.


in one case I boot a blob and it comes up with everything it needs and starts functioning immediately. there is no ambiguity in which code is executing since its exactly those bits that I constructed it with, and no external service dependencies.

if you work in a model where you never upgrade servers, just bring up new ones and turn down old ones, doesn't it seem cleaner? obviously they both work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: