What is docker container technology
Docker container technology refers to the fact that Docker is a container run by a program written in the GO language, which implements an application-level isolation; docker is designed for developers and system administrators to publish and an open platform for running distributed applications.
The operating environment of this tutorial: linux7.3 system, docker version 19.03, Dell G3 computer.
What is docker container technology
Docker container technology refers to Docker as a "container" (Linux containers, LXCs) run by a program written in the GO language. Docker implements an application level Isolation, it changes our basic development and operation unit from directly operating the virtual host (VM) to a "container" where the operating program runs.
Docker is an open platform designed for developers and system administrators to publish and run distributed applications. Composed of two parts: Docker Engine: a portable, lightweight runtime environment and package manager.
(Note* Single OS vs Single Thread) Docker Hub: A cloud service created for creating automated workflows and sharing applications. (Note* Cloud image/package management vs npm package management, is it particularly similar to npm?)
From March 20, 2013, the first version of Docker was officially released to Docker 1.0 in June 2014 It took 15 months for it to be officially released. Although its development history is very short, Docker is becoming more and more popular. In fact, Container technology is not an innovation of Docker. Cloud service providers such as HeroKu and NodeJitsu have adopted similar lightweight virtualization technology. However, Docker was the first to open source this Container technology on a large scale and was widely accepted by the community.
Container technology expansion
In the computer world, containers have a long and legendary history. Containers are different from hypervisor virtualization HV. Hypervisor virtualization uses an intermediate layer to virtualize one or more independent machines on physical hardware, while containers run directly on the operating system kernel. user space. Therefore, container virtualization is also called "operating system level virtualization". Container technology allows multiple independent user spaces to run on the same host.
Due to "guesting" in the operating system, the container can only run the same or similar operating system as the underlying host, which does not seem to be very flexible. For example: you can run Redhat Enterprise Linux in an Ubuntu service, but you cannot run Microsoft Windows on an Ubuntu server.
Containers are considered insecure relative to completely isolated hypervisor virtualization. Those who oppose this view believe that because virtual containers virtualize a complete operating system, this undoubtedly increases the scope of attacks, and the potential exposure risk of the hypervisor layer must also be considered.
Despite many limitations, containers are widely deployed in a variety of applications. Container technology is very popular in very large-scale multi-tenant service deployments, lightweight sandboxes, and isolation environments with less stringent security requirements. One of the most common examples is a "chroot jail", which creates an isolated directory environment to run processes. If the process running in the permission isolation prison is breached by an intruder, the intruder will find himself "in jail", trapped in the directory created by the container due to insufficient permissions, and unable to further damage the host machine.
The latest container technology introduces OpenVZ, Solaris Zones and Linux Containers (LXC). With these new technologies, containers are no longer just a simple operating environment. Within its own permission class, a container is more like a complete host. For Docker, it benefits from modern Linux features, such as control group and namespace technology. The isolation between the container and the host is more complete. The container has an independent network and storage stack, and also has Its own resource management capabilities enable multiple containers in the same host to coexist in a friendly manner.
Containers are considered a lean technology because containers require limited overhead. Compared with traditional virtualization and paravirtualization, containers do not require an emulation layer (emulation layer) and a management layer (hypervisor layer), but use the system call interface of the operating system. This reduces the overhead required to run a single container and allows more containers to be run on the host.
Despite their glorious history, containers are still not widely recognized. A very important reason is the complexity of container technology: containers themselves are complex, difficult to install, and difficult to manage and automate. And Docker was born to change all this.
Recommended learning: "docker video tutorial"
The above is the detailed content of What is docker container technology. 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)

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".

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.

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).

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).

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

Create a container in Docker: 1. Pull the image: docker pull [mirror name] 2. Create a container: docker run [Options] [mirror name] [Command] 3. Start the container: docker start [Container name]

The methods to view Docker logs include: using the docker logs command, for example: docker logs CONTAINER_NAME Use the docker exec command to run /bin/sh and view the log file, for example: docker exec -it CONTAINER_NAME /bin/sh ; cat /var/log/CONTAINER_NAME.log Use the docker-compose logs command of Docker Compose, for example: docker-compose -f docker-com
