Category: DevOps

Large web deployments like Google and Twitter, and platform providers such as Heroku
and dotCloud all run on container technology, at a scale of hundreds of thousands or
even millions of containers running in parallel.

In order to stop the Docker container you can use the below command:

docker stop <container ID>

Now to restart the Docker container you can use:

docker restart <container ID>

We can use Docker image to create Docker container by using the below command:

docker run -t -i <image name> <command name>

This command will create and start container.
You should also add, If you want to check the list of all running container with
status on a host use the below command:

docker ps -a

You can use json instead of yaml for your compose file, to use json file with compose,
specify the filename to use for eg: docker-compose -f docker-compose.json up

Docker can build images automatically by reading the instructions from a Dockerfile.
A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Using docker build users can create an automated build that executes several command-line instructions in succession.

It is native clustering for Docker which turns a pool of Docker hosts into a single, virtual Docker host. Docker Swarm serves the standard Docker API, any tool that already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts.
Some supported tools:
• Dokku
• Docker Compose
• Docker Machine
• Jenkins

Docker containers are easy to deploy in a cloud. It can get more applications running on
the same hardware than other technologies, it makes it easy for developers to quickly
create, ready-to-run containerized applications and it makes managing and deploying
applications much easier. You can even share containers with your applications.
If you have some more points to add you can do that but make sure the above the above
explanation is there in your answer.

Docker hub is a cloud-based registry service which allows you to link to code repositories, build your images and test them, stores manually pushed images, and links to Docker cloud so you can deploy images to your hosts. It provides a centralized resource for container image discovery, distribution and change management, user and team collaboration, and workflow automation throughout the development pipeline.

Docker containers include the application and all of its dependencies but share the kernel with other containers, running as isolated processes in user space on the host operating system. Docker containers are not tied to any specific infrastructure: they run on any
computer, on any infrastructure, and in any cloud.

Docker containers can be created by either creating a Docker image and then running it or you can use Docker images that are present on the Dockerhub.

Docker containers are basically runtime instances of Docker images.

Docker image is the source of Docker container. In other words, Docker images are used
to create containers. Images are created with the build command, and they’ll produce a
container when started with run. Images are stored in a Docker registry such as
registry.hub.docker.com because they can become quite large, images are designed to
be composed of layers of other images, allowing a minimal amount of data to be sent
when transferring images over the network.