Why docker is not a container
From the moment containerization technology was born, Docker has become a leader in this field. However, one voice is getting louder and louder, and it has to do with Docker not being a "container." This sentence is incredible, because Docker has always been synonymous with containerization technology, and people are talking about Docker Container.
So, why do some people say that Docker is not a "container"? How to understand this problem? This article will analyze why Docker is not a "container" from the perspective of technical implementation principles and philosophy.
- Technical Implementation Principle
Docker’s original idea was not containerization, but to encapsulate it based on LXC (Linux Container) and present it with a set of REST APIs Come out and make it easier for application developers to use it. This is the original idea of Docker. Docker technology initially supports single-process programs, which is based on submitting an Image image file. Once the image is submitted, Docker can start one or more containers through the image, and the application process is running in the container.
Compared with traditional virtualization technologies (such as VMWare, Virtual Box), Docker uses process-level isolation, that is, multiple containers on the same host can share the same set of operating system kernels. This can save a lot of resource overhead and easily achieve features such as rapid deployment, quick startup, quick migration, and version management.
In fact, Docker technology has improved and improved the original LXC technology and encapsulated it into a more lightweight and powerful container engine. From this perspective, Docker is not a native container technology, but an encapsulation and enhancement of containers, so some people say that Docker is not a "container".
- Philosophical level
In addition, there is another issue to consider from the philosophical level of Docker. Docker does not really install, configure, run and install "containers". Remove these aspects of management. In Docker, image building, updating, and version control are still managed by developers themselves. This means that Docker has not fully developed a unified mechanism to manage containers and images, which requires more or less manual work.
Moreover, Docker encapsulates the underlying container technology too much, making it too complex and easily confusing for beginners. And it contains too many pitfalls and limitations, which complicates containerization, a method that originally simplifies the process.
From this perspective, especially from the engineering implementation level, Docker cannot be classified as a "container" because it still needs to be improved mechanically.
- Is Docker a container?
Since the answer to the above two points is "no", what are the nature and characteristics of the Docker system? There is no doubt that Docker is a solution for application environment deployment and management, which is closely related to container technology. The benefits of Docker lie in its excellent operational simplicity, efficient sandbox mechanism, convenient image creation and sharing methods, and convenience in deploying containers. What Docker brings to people is a more scientific, faster and more convenient deployment method. Therefore, Docker can be seen as an application environment solution rather than a "container" dry matter.
Summary
This article explains why some people say that Docker is not a "container" from two aspects: Docker technology implementation principle and philosophical level. In fact, Docker is defined as a solution for application environment deployment and management. This does not mean that Docker replaces or does not require container technology, but it shows that Docker technology is based on the enhancement of container technology and better realizes the value of container technology. Although the nature and characteristics of Docker are not containers, the changes brought by Docker are a major leap forward in application environment management, bringing great convenience and flexibility.
The above is the detailed content of Why docker is not a container. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Four ways to exit Docker container: Use Ctrl D in the container terminal Enter exit command in the container terminal Use docker stop <container_name> Command Use docker kill <container_name> command in the host terminal (force exit)

Methods for copying files to external hosts in Docker: Use the docker cp command: Execute docker cp [Options] <Container Path> <Host Path>. Using data volumes: Create a directory on the host, and use the -v parameter to mount the directory into the container when creating the container to achieve bidirectional file synchronization.

How to restart the Docker container: get the container ID (docker ps); stop the container (docker stop <container_id>); start the container (docker start <container_id>); verify that the restart is successful (docker ps). Other methods: Docker Compose (docker-compose restart) or Docker API (see Docker documentation).

You can query the Docker container name by following the steps: List all containers (docker ps). Filter the container list (using the grep command). Gets the container name (located in the "NAMES" column).

The process of starting MySQL in Docker consists of the following steps: Pull the MySQL image to create and start the container, set the root user password, and map the port verification connection Create the database and the user grants all permissions to the database

Docker container startup steps: Pull the container image: Run "docker pull [mirror name]". Create a container: Use "docker create [options] [mirror name] [commands and parameters]". Start the container: Execute "docker start [Container name or ID]". Check container status: Verify that the container is running with "docker ps".

The steps to update a Docker image are as follows: Pull the latest image tag New image Delete the old image for a specific tag (optional) Restart the container (if needed)

DockerVolumes ensures that data remains safe when containers are restarted, deleted, or migrated. 1. Create Volume: dockervolumecreatemydata. 2. Run the container and mount Volume: dockerrun-it-vmydata:/app/dataubuntubash. 3. Advanced usage includes data sharing and backup.
