Blog

Problem with virturalization is that guest Operating System taking up too much space. This becomes rather wasteful when we’re horizontally scaling, and have multiple of instance, we’ll be essentially have same OS on each instance that are not doing anything useuful.

SO HERE COMES CONTAINER

we still have host hardware, and host os, but we have container engineer and have multiple apps running. It’s more condensed than virturalization.

Docker Image:
This is what container is made of; layers of images. And they’re readonly; they never change after they’re created. So special Read/Write layer is populated which allow them to read/write app(?)

Container Registry:
You can use docker hub to upload your container or download other’s container.

Key concept:

• Dockerfiles are used to build images
• Portable, self-contained, always run as intended
• Lightweight; parent os used, fs layers are shared
• Container only runs the application & environment it needs