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

This article mainly shows you "how to use the run command in docker". The content is simple and clear. I hope it can help you solve your doubts. Let the editor lead you to study and learn how to use the run command in docker.

First, take a look at the command format:

Docker run [OPTIONS] IMAGE [: TAG] [COMMAND] [ARG...]-d,-- detach=false specifies whether the container runs in the foreground or background. The default is false-I,-- interactive=false opens STDIN for console interaction-t,-- tty=false to assign tty devices, which can support terminal login. The default is false-u,-- user= "" specifies the user of the container-a,-- attach= [] logs in to the container (must be a container started with docker run-d)-w,-- workdir= "" specifies the working directory of the container-c,-- cpu-shares=0 sets the container CPU weight Use-e,-- env= [] to specify environment variables in CPU sharing scenarios You can use this environment variable-m,-- memory= "" to specify the upper limit of the container's memory-P,-- publish-all=false to specify the port exposed by the container-p,-- publish= [] to specify the port exposed by the container-h,-- hostname= "" to specify the hostname of the container-v -- volume= [] mounts the storage volume to the container Mount to a directory of the container-- volumes-from= [] mounts volumes on other containers to the container, and mount to a directory of the container-- cap-add= [] add permissions-- cap-drop= [] delete permissions-- after cidfile= "" runs the container, writes the container pid value in the specified file. A typical use of monitoring system-cpuset= "" sets which CPU can be used by the container. This parameter can be used to monopolize the CPU of the container-- device= [] add host devices to the container. Equivalent to device pass-through-dns= [] specifies the dns server of the container-- dns-search= [] specifies the dns search domain name of the container, and writes to the container's / etc/resolv.conf file-- entrypoint= "" overrides the entry point of image-- env-file= [] specifies the environment variable file. The file format is one environment variable per line-- expose= [] specifies the port exposed by the container, that is, modifies the exposed port of the image-- link= [] specifies the association between containers, and specifies the configuration file of the container using information such as IP and env of other containers-- lxc-conf= []. Use-- name= "" to specify the container name only when you specify-- exec-driver=lxc. Container management can be done later by name. The links feature requires the name net= "bridge" container network setting: bridge uses the bridge specified by docker daemon host / / the container uses the host's network container:NAME_or_ID > / / uses the network of other containers Sharing network resources such as IP and PORT the none container uses its own network (similar to-- net=bridge), but does not configure it-- privileged=false specifies whether the container is a privileged container The privileged container owns all the capabilities-- restart= "no" specifies the restart policy after the container is stopped: no: do not restart when the container exits on-failure: restart when the container fails to exit (the return value is non-zero) always: container Always restart on exit-rm=false specifies that containers are automatically deleted after the container stops (containers started with docker run-d are not supported)-sig-proxy=true settings are accepted and processed by the agent But SIGCHLD, SIGSTOP and SIGKILL cannot be represented

The above are some of the commonly used parameters of run.

So let's give some common examples.

Case 1. Run a simple container that contains console management

[root@localhost] # docker run-I-t centos7.2

As soon as the container is executed, it goes to the default thread "/ bin/bash" and goes directly to the console operation. After exiting control, the container is terminated.

Case 2. Run a container executed in the background, and at the same time, it can be managed by the console.

[root@localhost] # docker run-d-I-t centos7.2

As soon as this container executes, it automatically executes the default thread "/ bin/bash", but does not allow you to immediately enter the console operation. It will be executed in the background, and you can see the currently running console with docker ps. You can use docker attach "Container name or id" to enter the container.

Case 3. Run a container with commands in the background without directly displaying the internal information of the container.

[root@localhost] # docker run-d centos7.2 ping www.baidu.com

This container will be executed permanently in the background because the ping thread will not stop. Unless you stop the thread of ping.

Case 4. Run a container that is constantly executed in the background, with commands, restart and run after the program is terminated, and can be managed by the console

[root@localhost] # docker run-d-restart=always centos7.2 ping www.baidu.com

This container will be executed permanently in the background because the ping thread will not stop. If you terminate the ping thread, the container will restart to continue the ping function.

Case 5. We need to specify a name for the container

[root@localhost] # docker run-d-name=server-db centos7.2 / usr/bin/mysql_safe-d

At this time, the name of our container is server-db, and the background thread of the database mysql is activated to keep it running, so that our container will not be closed.

Case 6. We need to connect the server-http container to the server-db container

[root@localhost] # docker run-d-name=server-http-- link=server-db centos7.2 / usr/bin/httpd-- DFOREGROUND

At this time, we executed the server of apache to keep it running in the background, and at the same time, configure the server name of mysql in php as "server-db", and just name it with server-db. You don't need to enter an ip address or anything like that. Our server-http specification is connected to server-db. Server-db will be treated as a DNS parse in server-http to get the corresponding connection ip.

Case 7. We are going to expose the port of server-db,server-http for everyone to visit

[root@localhost] # docker run-d-- name=server-db-p 3306 name=server-db 3306 centos6.8-mysql / usr/bin/mysql_safe-d

At this time, we specify that port 3306 of the server host is mapped to port 3306 of the container and exposed.

[root@localhost] # docker run-d-- name=server-http-- link=server-db-p 8080:80centos6.8-httpd / usr/bin/httpd-- DFOREGROUND

At this time, we specify that port 8080 of the server host is mapped to port 80 of the container and exposed.

Case 8. We want to mount the host's database directory / server/mysql-data to the server-db

[root@localhost] # docker run-d-- name=server-db-p 3306 name=server-db 3306-v / server/mysql-data:/mysql-data centos6.8-mysql / usr/bin/mysql_safe-d

At this point, you will find that in the server-db root directory you will find a new folder mysql-data, and the contents of the files are the same as the host / server/mysql-data.

Case 9. We want a container to be automatically deleted as soon as its process ends.

[root@localhost] # docker run-ti-- the above is all the content of the article "how to use run commands in docker". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to 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.