3 ms·
Containers and VMs are totally not the same thing. They serve a complete other purpose , as multiple containers can be combined to create an application/service
by r3mc0 4y ago
Containers and VMs are totally not the same thing.
They serve a complete other purpose , as multiple containers can be combined to create an application/service , VMs always use a complete os etc etc anyway the internet is full of the true purpose of containers , they were never meant to use as a "VM" and about security.. meh everything is insecure until proven differently
- wongarsu 4y agoVMs can have private networks between each other just as containers do. That's pretty much what EC2 is about.
- kazen44 4y agoheck, when running something in production with multiple underlying servers, you need a system that builds an overlay network regardless if you use containers or Vm's..
- nijave 4y agoVMs don't need a full OS. You can run a single process directly from the kernel with no init system or other userland
- R0flcopt3r 4y agoMaybe you should read the article? The article basically covers running a tiny kernel that as exactly what you need to run one single binary, which is your application. No printer drivers, video drivers. Probably have network drivers, as that would be quite handy. Kinda up to you on what kernel you pick for this, and what drivers are included. Multiple VMs with networking can also be "combined"... Containers are great because they are small and fast, low overhead etc. And that is why they replaced virtual machines. This article however proves that this is also achievable with virtual machines.