Introduction to Docker in 10 mints

Story ends Here?

We need to troubleshoot and fix it. It is a never-ending story. Most of us have a lot of such experiences with a sleepless night.

Do you like to continue the rest of your professional life like this?

What is the solution to this problem?

• Each goods item needs to treat separately

If we need to transport a car, we need to take it to the port with some suitable transporting method and then load it to the ship. The same applies to spices or fish; it needs to treat as it is. Most of the time we can not use any modern equipment like a crane or other moving equipment.

• It consumes lots of time

Since each item needs to handle separately, we can not use any commonly used equipment to move it. Because of this, it takes lots of time to load and unload the goods.

• The loss and damage of the goods items were higher

Here we can not keep spices or fish nearby, which will damage both. So while placing the items, we need to take utmost care.

They introduced a standard container. We can load any goods item in the container and sealed it from the manufacturing unit. It is easy to use different movement and transporting equipment. We can use any equipment shown at the bottom of the picture. Here each item is loads in an isolated container. So we do not need to be much worried about what is in each container.

In the above example, the shipping industry introduced a standard container and packed everything in it. That helped the easy management of containers.

In the same way, the docker packs the application code, supporting packages, binaries and other dependencies along with the operating system. Let it be MySQL, Mongo DB, Nginx or Redis or any other application. Once we pack it inside a docker image, we can treat it like a container.

• We have a web application

• We install the webserver

• Install its dependency

• Copy the web content

• With this, we will make a container image

• Push it to the Docker registry

• Pull it from the registry

• Run it as container

When we need to run a web server, we will pull it from the registry and run it as a container. Since it is a lightweight image, it is easy and quick to pull and run.

In the Docker world, we pack the code along with its dependency in a container image. The containers are running from those images, so we will not end up in dependency issues. It is like we ask the developer to send the application code along with her laptop. And we use that laptop to serve the production application. In reality, we can not use a desktop computer in place of a production-grade server. It is just to show you that how containerisation helps in avoiding the dependency issue.