Docker-Technology stack

Similar to the traditional approach, building and running Docker containers is similar to building and running programs on a virtual machine, just using a new set of tools and techniques.

Unlike virtual machines, Docker containers increase flexibility by isolating host hosts from applications or services, but with the introduction of additional container embedding layers, some overhead is added.

The typical Docker technology stack contains components that address the focus: Building Systems

How to build the image and push it into the mirror repository.

Mirrored Warehouse

Where the Docker image is saved.

Homestay Host Management

Because the Docker image contains the application and its dependencies (self-system), the management of the host becomes simpler. Typically, you only need to add new servers, configure access rights and firewalls, and install the Docker daemon.

Configuration Management Deployment

There are two ways of mirroring deployment:

1. Push-Deploy or orchestrate the system to push the image to a designated host

2. Pull-Gets the image file from the mirrored warehouse on the host.

Choreography

Includes operations on all aspects of the container. For example, how to organize container clusters, run those containers on those servers (host), how to schedule containers, how to expose/discover containers, and so on.

Docker-Technology stack