Shulou(Shulou.com)06/01 Report--

This article is to share with you about how to deploy the Docker project more elegantly. The editor thinks it is very practical, so I share it with you. I hope you can get something after reading this article.

If you need to deploy the same project more than once, if you have ever encountered the problem of "obviously running well on my computer", if you have heard of Docker but have not used it, if you are not sure whether you need Docker in the end, then I hope you will take the time to read this article!

Because Docker will help you easily run open source projects written in languages you are not familiar with, help you deploy your projects more elegantly, and save you the tedious process of downloading and configuring your environment.

Now let's take a look at it and preview the actual effect of a Docker-based deployment project, hoping to give you a first impression of Docker!

Nginx deployed by Docker acts as a reverse proxy server, supporting https access and pan-domain name resolution.

Experience address: https://snowdreams1006.cn/

Docker deployed letsencrypt free production of pan-domain name certificate and integration of reverse proxy service nginx to achieve https access.

> experience address: https://www.snowdreams1006.cn/

Docker deploys nginx as a static server and deploys static websites to demonstrate static blog functions.

Experience address: https://resume.snowdreams1006.cn/

Docker deploys bark as a back-end server and deploys an open source project to act as a message push server.

Experience address: https://bark.snowdreams1006.cn/ping

Docker deploys webhook as a back-end server and deploys an open source project to receive callbacks from Webhook events.

Experience address: https://webhook.snowdreams1006.cn/hooks/github

Blog deployed by Docker is used as a static server to automatically update blog content and push messages based on Github Action or Webhook.

After the content of the Github repository is updated, Github Action is triggered to automatically build and deploy the remote server static blog, and the Webhook event is sent to the webhook hook container, and then the bark message push container is called to realize the message push to Wechat message and app notification.

After updating the Github warehouse, automatically run the Github Action source code to build a static blog and upload it to the remote server, and the blog container will immediately restart to complete the content update.

The Github warehouse updates and sends Webhooks to the remote server. After receiving the request, the webhook container forwards it to the bark container, and then pushes it to the mobile phone.

Whether familiar open source projects or unfamiliar open source projects, Docker makes these differences the same, unified management makes the use of costs greatly reduced, more elegant deployment of the project, really more than just talk!

prerequisite

Currently, when Docker is installed on a Linux system, the system version is required as follows:

CentOS: 7

Debian: 7.7 (Wheezy LTS), 8.0 (Jessie LTS), 9 (Stretch)

Fedora: 24 、 25

Ubuntu: 16.04 (Xenial LTS), 14.04 (Trusty LTS), 17.04 (Zesty)

On the one hand, the above prerequisites are basically met by the new server, on the other hand, the author has not conducted an in-depth experiment on this. Please verify it by yourself. The following mainly takes Centos7.6 as an example to explain how to install Docker.

Verification environment

For beginners, although it is very easy to install Docker, it is inevitable to encounter some unexpected situations, perhaps an installation error requires reinstallation or is not sure whether the remote server has been installed, so check to see if Docker has been installed before you start the installation.

Call the docker command

First connect to the remote server and run the docker command. If you output a lot of usage instructions like below, it proves that Docker has been successfully installed and may have configured the relevant environment.

The only thing you need to do now is to learn the basic usage of Docker, because you don't have to install the Docker environment yourself, and you basically don't have to look down.

[root@snowdreams1006] # dockerUsage: docker [OPTIONS] COMMANDA self-sufficient runtime for containersOptions:-- config string Location of client config files (default "/ root/.docker")-c,-- context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")-D,-- debug Enable debug mode-H,-- host list Daemon socket (s) to connect to-l -log-level string Set the logging level ("debug" | "info" | "warn" | "error" | "fatal") (default "info")-- tls Use TLS Implied by-tlsverify-tlscacert string Trust certs signed only by this CA (default "/ root/.docker/ca.pem")-tlscert string Path to TLS certificate file (default "/ root/.docker/cert.pem")-tlskey string Path to TLS key file (default "/ root/.docker/key.pem")-tlsverify Use TLS and verify the remote-v -- version Print version information and quitManagement Commands: builder Manage builds config Manage Docker configs container Manage containers context Manage contexts engine Manage the docker engine image Manage images network Manage networks node Manage Swarm nodes plugin Manage plugins secret Manage Docker secrets service Manage services stack Manage Docker stacks swarm Manage Swarm system Manage Docker trust Manage trust on Docker images volume Manage volumesCommands: attach Attach local standard input, output And error streams to a running container build Build an image from a Dockerfile commit Create a new image from a container's changes cp Copy files/folders between a container and the local filesystem create Create a new container diff Inspect changes to files or directories on a container's filesystem events Get real time events from the server exec Run a command in a running container export Export a container's filesystem as a tar archive history Show the history of an image images List images import Import the contents from a tarball to create a filesystem image info Display system-wide information inspect Return low-level information on Docker objects kill Kill one or more running containers load Load an image from a tar archive or STDIN login Log in to a Docker registry logout Log out from a Docker registry logs Fetch the logs of a container pause Pause all processes within one or more containers port List port mappings or a specific mapping for the container ps List containers pull Pull an image or a repository from a registry push Push an image or a repository to a registry rename Rename a container restart Restart one or more containers rm Remove one or more containers rmi Remove one or more images run Run a command in a new container save Save one or more images to a tar archive (streamed to STDOUT by default) search Search the Docker Hub for images start Start one or more stopped containers stats Display a live stream of container ) resource usage statistics stop Stop one or more running containers tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE top Display the running processes of a container unpause Unpause all processes within one or more containers update Update configuration of one or more containers version Show the Docker version information wait Block until one or more containers stop Then print their exit codesRun 'docker COMMAND-- help' for more information on a command.

If you type the docker prompt command not found, it is very likely that the server does not have the Docker environment installed. Here is how to install the Docker environment step by step!

Install Docker

Step 1: remove the old version

Sudo yum remove docker\ docker-client\ docker-client-latest\ docker-common\ docker-latest\ docker-latest-logrotate\ docker-logrotate\ docker-engine

This step is optional because the name of the latest version of Docker has changed. To ensure that the latest version of Docker-CE is installed, uninstall the old version that may have been installed first.

Step 2: install necessary system dependencies

Sudo yum install-y yum-utils device-mapper-persistent-data lvm2

Install some necessary dependencies, just follow the official tutorial instructions, even if the system already exists in the environment can be run again, rest assured to copy and paste it!

Step 3: add software source information

Sudo yum-config-manager-- add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo

Step 4: update the yum cache

Sudo yum makecache fast

Step 5: install docker-ce

Sudo yum-y install docker-ce

If there are no errors during the above installation, the basic Docker environment is now installed!

Start Docker

View statu

Sudo systemctl status docker

By default, the Docker service will not be started automatically after the initial installation, and the output of checking the running status will not include Active: active (running) but Active: inactive (dead).

Start for the first time

Sudo systemctl start docker

After installation, the Docker service is not started by default, so you need to start the Docker service first after installation. If you check the running status again, sudo systemctl status docker should be running Active: active (running).

Restart

Sudo systemctl restart docker

You can restart if the Docker service has been stopped or if it has already been started.

Out of Service

Sudo systemctl stop docker

If there is a problem with the running Docker and needs to stop the maintenance, you can stop the Docker service first, and after the maintenance is over, you can run sudo systemctl start docker to start the service again.

Check self-booting

Systemctl list-unit-files | grep enabled | grep docker

Check whether the Docker service will boot automatically. If there is a result, it will boot. If there is no result, it will not boot.

Self-booting

Sudo systemctl enable docker

Docker service is a very important process service, which generally needs to be booted automatically to ensure that the service can be restored after accidental shutdown.

Prohibit self-booting

Sudo systemctl disable docker

If you accidentally set up boot and you really don't plan to boot, you can disable the boot feature and the Docker service will not start automatically the next time your computer restarts.

View version

Docker version

Looking at the currently installed Docker version information, you can see that it is mainly divided into two parts: Client: Docker Engine-Community and Server: Docker Engine-Community.

[root@snowdreams1006 ~] # docker versionClient: Docker Engine-Community Version: 19.03.5 API version: 1.40 Go version: go1.12.12 Git commit: Wed Nov 13 07:25:41 2019 OS/Arch: linux/amd64 Experimental: falseServer: Docker Engine-Community Engine: Version: 19.03.5 API version: 1.40 ( Minimum version 1.12) Go version: go1.12.12 Git commit: 633a0ea Built: Wed Nov 13 07:24:18 2019 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.2.10 GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339 runc: Version: 1.0.0-rc8+dev GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657 docker-init: Version: 0.18.0 GitCommit: fec3683

Now you don't have to care about the specific version information, as long as you can output similar information after running the docker version command, and then start the real show!

Mirror acceleration

The Docker service has been installed and started, and then we can deploy applications based on Docker. Of course, there is still a long way to go to actually deploy our own applications, but we can run public applications!

The first thing to learn any new language is to run hello world, and learning Docker containerization deployment is no exception. We also run the Docker version of hello world!

When we type in the docker run hello-world command, the terminal will output the following, as long as the output Hello from Docker! The words prove that the environment has been built!

[root@snowdreams1006] # docker run hello-worldUnable to find image 'hello-world:latest' locallylatest: Pulling from library/hello-world1b930d010525: Pull complete Digest: sha256:4df8ca8a7e309c256d60d7971ea14c27672fc0d10c5f303856d7bc48f8cc17ffStatus: Downloaded newer image for hello-world:latestHello from docking this message shows that your installation appears to be working correctly.To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.To try something more ambitious, you can run an Ubuntu container with: $docker run-it ubuntu bashShare images, automate workflows, and more with a free Docker ID: https://hub.docker.com/For more examples and ideas, visit: https://docs.docker.com/get-started/[root@snowdreams1006 ~]

If your network speed is slow, the above process may take some time, but if your network speed is average and the above process is extremely slow, it is probably because you do not configure mirroring!

Because Docker defaults to download the project from abroad to the local, and then run the service, as we usually visit Github, the network speed is not generally slow!

Github cannot speed up access without an image acceleration address, but Docker project repositories do have image repositories. There are many domestic image service providers that basically need to register an account to obtain image addresses and so on.

Here is the address of NetEase's image repository http://hub-mirror.c.163.com and Aliyun's personal image repository address https://8upnmlh4.mirror.aliyuncs.com.

As long as you configure the image address to Docker, the next time you download the project, the speed should be significantly improved!

It is preferred to open and edit the / etc/docker/daemon.json file, and if not, create a new file, as follows:

{"registry-mirrors": ["http://hub-mirror.c.163.com"]}"

Will it be quick to restart the Docker service after saving and try running docker pull nginx?

Uninstall docker

If you find that you accidentally want to reinstall the Docker service or just want to uninstall Docker, you can simply run the following command to clean up the Docker environment!

Sudo yum remove docker-cesudo rm-rf / var/lib/docker

Running the docker command again at this point will prompt command not found to look forward to a new look when we meet again!

Basic command

As we first met, when we successfully installed Docker, the console output a lot of introductions about usage, but I didn't care when I was young and frivolous at that time. I suddenly looked back and found it so useful!

[root@snowdreams1006] # dockerUsage: docker [OPTIONS] COMMANDA self-sufficient runtime for containersOptions:-- config string Location of client config files (default "/ root/.docker")-c,-- context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")-D,-- debug Enable debug mode-H,-- host list Daemon socket (s) to connect to-l -log-level string Set the logging level ("debug" | "info" | "warn" | "error" | "fatal") (default "info")-- tls Use TLS Implied by-tlsverify-tlscacert string Trust certs signed only by this CA (default "/ root/.docker/ca.pem")-tlscert string Path to TLS certificate file (default "/ root/.docker/cert.pem")-tlskey string Path to TLS key file (default "/ root/.docker/key.pem")-tlsverify Use TLS and verify the remote-v -- version Print version information and quitManagement Commands: builder Manage builds config Manage Docker configs container Manage containers context Manage contexts engine Manage the docker engine image Manage images network Manage networks node Manage Swarm nodes plugin Manage plugins secret Manage Docker secrets service Manage services stack Manage Docker stacks swarm Manage Swarm system Manage Docker trust Manage trust on Docker images volume Manage volumesCommands: attach Attach local standard input, output And error streams to a running container build Build an image from a Dockerfile commit Create a new image from a container's changes cp Copy files/folders between a container and the local filesystem create Create a new container diff Inspect changes to files or directories on a container's filesystem events Get real time events from the server exec Run a command in a running container export Export a container's filesystem as a tar archive history Show the history of an image images List images import Import the contents from a tarball to create a filesystem image info Display system-wide information inspect Return low-level information on Docker objects kill Kill one or more running containers load Load an image from a tar archive or STDIN login Log in to a Docker registry logout Log out from a Docker registry logs Fetch the logs of a container pause Pause all processes within one or more containers port List port mappings or a specific mapping for the container ps List containers pull Pull an image or a repository from a registry push Push an image or a repository to a registry rename Rename a container restart Restart one or more containers rm Remove one or more containers rmi Remove one or more images run Run a command in a new container save Save one or more images to a tar archive (streamed to STDOUT by default) search Search the Docker Hub for images start Start one or more stopped containers stats Display a live stream of container ) resource usage statistics stop Stop one or more running containers tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE top Display the running processes of a container unpause Unpause all processes within one or more containers update Update configuration of one or more containers version Show the Docker version information wait Block until one or more containers stop Then print their exit codesRun 'docker COMMAND-- help' for more information on a command. Self introduction

The first paragraph of the usage introduction is self-introduction, the usage is: docker [OPTIONS] COMMAND, that is, docker + optional options + required commands.

The implication is that A self-sufficient runtime for containers provides a self-contained running environment for the container!

Usage: docker [OPTIONS] COMMANDA self-sufficient runtime for containers

Docker is like a super freighter in life, transporting containers of uniform specifications, while containers carry a variety of goods to different destinations.

The container is a container, the freighter provides a self-contained environment for the container, and the containers are independent of each other, which is a simple explanation of the first paragraph.

Option configuration

Let's move on to the second paragraph, which mainly explains the configuration items and the specific meaning behind these configuration items.

Options:-- config string Location of client config files (default "/ root/.docker")-c,-- context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")-D,-- debug Enable debug mode-H,-- host list Daemon socket (s) to connect to-l -log-level string Set the logging level ("debug" | "info" | "warn" | "error" | "fatal") (default "info")-- tls Use TLS Implied by-tlsverify-tlscacert string Trust certs signed only by this CA (default "/ root/.docker/ca.pem")-tlscert string Path to TLS certificate file (default "/ root/.docker/cert.pem")-tlskey string Path to TLS key file (default "/ root/.docker/key.pem")-tlsverify Use TLS and verify the remote-v,-version Print version information and quit

As long as people with a certain knowledge of English should be able to understand the meaning, if they are not very clear about personal details, they can copy and paste them into the browser for online translation.

No message saw the last-v,-- version option, which means print version information and exit.

When we see here, we understand that the docker version that ran before is not the same thing as the version here.

[root@snowdreams1006] # docker-vDocker version 19.03.5, build 633a0ea [root@snowdreams1006 ~] # docker-- versionDocker version 19.03.5, build 633a0ea

Purely from the output, docker-version is more concise, if only to verify whether the environment installation is successful, or to run docker-version is relatively straightforward.

Management command

The third part is the management commands supported by Docker. Let's not delve into the details now, as long as you have an impression. Note that there is a command about mirroring, docker image.

Management Commands: builder Manage builds config Manage Docker configs container Manage containers context Manage contexts engine Manage the docker engine image Manage images network Manage networks node Manage Swarm nodes plugin Manage plugins secret Manage Docker secrets service Manage services stack Manage Docker stacks swarm Manage Swarm system Manage Docker trust Manage trust on Docker images volume Manage volumes

Because the usage in the self-introduction is docker [OPTIONS] COMMAND, and the bracket [] indicates that the content is optional, the basic usage without any option is docker COMMAND, so the complete usage of the image command is: docker image.

[root@snowdreams1006 ~] # docker imageUsage: docker image COMMANDManage imagesCommands: build Build an image from a Dockerfile history Show the history of an image import Import the contents from a tarball to create a filesystem image inspect Display detailed information on one or more images load Load an image from a tar archive or STDIN ls List images prune Remove unused images pull Pull an image or a repository from a registry push Push an image or a repository to a registry rm Remove One or more images save Save one or more images to a tar archive (streamed to STDOUT by default) tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGERun 'docker image COMMAND-- help' for more information on a command.

There is also a subcommand in the management command, which is roughly the same as the previous introduction, and the basic usage is: docker image COMMAND.

Among the commands supported is ls, so the final complete command to invoke the ls command is: docker image ls.

# docker image lsREPOSITORY TAG IMAGE ID CREATED SIZEhello-world latest fce289e99eb9 11 months ago 1.84kB

The image installed on the server includes the familiar hello-world. As for what is REPOSITORY and what is IMAGE, there is no need to delve into it for the time being, just need to know how to use these commands without documentation!

If you pay attention, you can see Run 'docker image COMMAND-- help' for more information on a command. In a word, it seems that we have ready-made help documents for us to learn!

Take the ls command as an example to demonstrate how to use docker image COMMAND-- help to view help documentation.

[root@snowdreams1006] # docker image ls-- helpUsage: docker image ls [OPTIONS] [REPOSITORY [: TAG]] List imagesAliases: ls, images, listOptions:-a,-- all Show all images (default hides intermediate images)-- digests Show digests-f,-- filter filter Filter output based on conditions provided-- format string Pretty-print images using a Go template-- no-trunc Don't truncate output-Q -- quiet Only show numeric IDs

Although the sparrow has all the five organs, I didn't expect that the ls command has more fine-grained usage instructions, supporting optional parameters and [REPOSITORY [: TAG]], as well as ls, images, and list aliases!

If ls has aliases of images and list, doesn't that mean that docker image ls is equivalent to docker image images and docker image list?

[root@snowdreams1006 ~] # docker image listREPOSITORY TAG IMAGE ID CREATED SIZEhello-world latest fce289e99eb9 11 months ago 1.84kB [root@snowdreams1006 ~] # docker image imagesREPOSITORY TAG IMAGE ID CREATED SIZEhello-world latest Fce289e99eb9 11 months ago 1.84kB

From the above output results, the operation effect of the three is indeed the same, it seems that a new world has been discovered!

Ordinary command

Back to the main line of the docker command, in addition to the management command or ordinary command, this part of the command is also a frequently used command is also the focus of learning to master the command!

Commands: attach Attach local standard input, output And error streams to a running container build Build an image from a Dockerfile commit Create a new image from a container's changes cp Copy files/folders between a container and the local filesystem create Create a new container diff Inspect changes to files or directories on a container's filesystem events Get real time events from the server exec Run a command in a running container export Export a container's filesystem as a tar archive history Show the history of an image images List images import Import the contents from a tarball to create a filesystem image info Display system-wide information inspect Return low-level information on Docker objects kill Kill one or more running containers load Load an image from a tar archive or STDIN login Log in to a Docker registry logout Log out from a Docker registry logs Fetch the logs of a container pause Pause all processes within one or more containers port List port mappings or a specific mapping for the container ps List containers pull Pull an image or a repository from a registry push Push an image or a repository to a registry rename Rename a container restart Restart one or more containers rm Remove one or more containers rmi Remove one or more images run Run a command in a new container save Save one or more images to a tar archive (streamed to STDOUT by default) search Search the Docker Hub for images start Start one or more stopped containers stats Display a live stream of container ) resource usage statistics stop Stop one or more running containers tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE top Display the running processes of a container unpause Unpause all processes within one or more containers update Update configuration of one or more containers version Show the Docker version information wait Block until one or more containers stop Then print their exit codes

The commands are good, but don't be greedy. Find the simplest docker run and docker version commands you've just used.

Docker run: Run a command in a new container

To run a command in a new container and translate it into a living language is to do a mysterious operation in the container!

Docker version: Show the Docker version information

Display Docker version information, remember docker-version?

If you forget, flip up-- version is described as Print version information and quit, a simpler version of information.

Whether it is an administrative command or an ordinary command, there will be corresponding usage instructions and help information after entering the command directly, and just add-- help!

[root@snowdreams1006 ~] # docker run "docker run" requires at least 1 argument.See 'docker run-- help'.Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Run a command in a new container help

The last is the bright spot. Add-help at the end of the command to get more detailed help information, which is suitable not only for the first-level command docker image-- help but also for the second-level subcommand docker image ls-- help.

Run 'docker COMMAND-- help' for more information on a command.

So, when you encounter commands that you don't understand or don't know, be sure to remember-- help help command, which is the most important point of all docker commands!

Recollection summary

Docker is a standardized way of deployment, operation and maintenance, compared with the traditional packaging deployment, more unified and standardized, goods are a variety of just like the diversity of development languages, but the emergence of containers has subverted logistics and transportation, bringing great progress!

If you are a Java background developer, more or less must have your own independent deployment project experience, first log in to the server to install a Java environment and then install a Tomcat environment, and finally upload your own War package to the Tomcat deployment directory, such repeated tedious work does not necessarily guarantee one-time success!

Because sometimes your code is likely to have some absolute paths, deployment to the server will definitely report errors, if the lack of personal files will also report errors, and so on, then there is a classic dialogue: obviously running well on my computer ah!

The emergence of Docker solves this problem to some extent. The application is packaged into a container. Docker, as a super freighter, carries the container to the destination safely and quickly. The environment in the container is self-sufficient and closed, and all the related dependencies are given to you at one time.

Whether it is the local transport of this closed container or the remote server transport of this container, the result is the same, and there will no longer be mutual complaints caused by environmental inconsistencies!

So the question is, if you are given a container, can you safely and quickly transport it to your destination? If you already have a shipment on hand that needs this kind of container service, how can it be quickly packaged into a container?

For the first question, this article has given the answer, which is docker + docker COMMAND-the commands supported by the help query and the help documentation for the commands.

[root@snowdreams1006 ~] # dockerUsage: docker [OPTIONS] COMMANDA self-sufficient runtime for containersOptions:-- config string Location of client config files (default "/ root/.docker")-c,-- context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")-D -- debug Enable debug mode-H,-- host list Daemon socket (s) to connect to-l,-- log-level string Set the logging level ("debug" | "info" | "warn" | "error" | "fatal") (default "info")-- tls Use TLS Implied by-tlsverify-tlscacert string Trust certs signed only by this CA (default "/ root/.docker/ca.pem")-tlscert string Path to TLS certificate file (default "/ root/.docker/cert.pem")-tlskey string Path to TLS key file (default "/ root / .docker / key.pem ")-- tlsverify Use TLS and verify the remote-v -- version Print version information and quitManagement Commands: builder Manage builds config Manage Docker configs container Manage containers context Manage contexts engine Manage the docker engine image Manage images network Manage networks node Manage Swarm nodes plugin Manage plugins secret Manage Docker secrets service Manage services stack Manage Docker stacks swarm Manage Swarm system Manage Docker trust Manage trust on Docker images volume Manage volumesCommands: attach Attach local standard input, output And error streams to a running container build Build an image from a Dockerfile commit Create a new image from a container's changes cp Copy files/folders between a container and the local filesystem create Create a new container diff Inspect changes to files or directories on a container's filesystem events Get real time events from the server exec Run a command in a running container export Export a container's filesystem as a tar archive history Show the history of an image images List images import Import the contents from a tarball to create a filesystem image info Display system-wide information inspect Return low-level information on Docker objects kill Kill one or more running containers load Load an image from a tar archive or STDIN login Log in to a Docker registry logout Log out from a Docker registry logs Fetch the logs of a container pause Pause all processes within one or more containers port List port mappings or a specific mapping for the container ps List containers pull Pull an image or a repository from a registry push Push an image or a repository to a registry rename Rename a container restart Restart one or more containers rm Remove one or more containers rmi Remove one or more images run Run a command in a new container save Save one or more images to a tar archive (streamed to STDOUT by default) search Search the Docker Hub for images start Start one or more stopped containers stats Display a live stream of container ) resource usage statistics stop Stop one or more running containers tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE top Display the running processes of a container unpause Unpause all processes within one or more containers update Update configuration of one or more containers version Show the Docker version information wait Block until one or more containers stop Then print their exit codesRun 'docker COMMAND-- help' for more information on a command.

For the second question, please preview the docker related commands first. Thank you for your reading!

The above is how to deploy the Docker project more elegantly, and the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.