


What is the difference between entrypoint and cmd under docker?
The difference between entrypoint and cmd under docker is: 1. The CMD command runs an executable file and provides parameters. Parameters can be specified for ENTRYPOINT; 2. The ENTRYPOINT command itself can also contain parameters, and the changed parameters will not is covered.
The difference between entrypoint and cmd under docker is:
1. CMD command:
CMD provides some commands and parameters when the container is running. The usage is as follows:
CMD ["executable", "param1", "param2"] (exec form , this is the preferred form)
CMD ["param1","param2"] (as default parameters to ENTRYPOINT)
CMD command param1 param2 (shell form)
First usage: run an executable file and provide parameters.
Second usage: Specify parameters for ENTRYPOINT.
The third usage (shell form): is a command executed with the "/bin/sh -c" method.
If you specify:
CMD [“/bin/echo”, “this is a echo test ”]
run after build (assuming the image is named ec):
docker run ec
will output:
this is a echo test
Doesn’t it feel weird? Like startup items, you can temporarily understand it this way.
Note:
docker run
If the parameters are specified in the command, the parameters in the CMD will be overwritten: (Here To explain, for example: docker run -it ubuntu /bin/bash The parameters of the command refer to /bin/bash instead of -it, -it
is just a parameter of docker, not a parameter of the container, as described below The parameters are all the same.)
The same ec image startup above:
docker run ec /bin/bash
will not output:
this is a echo test
Because the CMD command is overwritten by "/bin/bash" .
2. ENTRYPOINT instruction
literally means entry point, and its function is exactly what it means. It allows your container to function like an executable program.
The container function behaves like an executable program. What does this mean?
Just give an example to make it easier to talk:
Example 1:
Use the following ENTRYPOINT to construct the image:
ENTRYPOINT ["/bin/echo"]
Then the container after the image built by docker The function is like a /bin/echo program:
For example, the name of the image I built is imageecho, then I can use it like this:
docker run -it imageecho “this is a test”
"this is a test" will be output here This string of characters, and the container corresponding to this imageecho image behaves like an echo program. The parameter "this is a test" you added will be added after ENTRYPOINT, and it will become like this /bin/echo "this is a test". Now you should understand what the entry point means.
Example 2:
ENTRYPOINT ["/bin/cat"]
You can run the constructed image like this (assuming it is named st):
docker run -it st /etc/fstab
This is equivalent to: /bin/cat /etc /fstab
What this command does. After running, the contents in /etc/fstab
will be output.
ENTRYPOINT has two ways of writing:
Writing method one:
ENTRYPOINT ["executable", "param1", "param2"] (the preferred exec form)
Writing method two:
ENTRYPOINT command param1 param2 (shell form)
You can also docker run Use –entrypoint to specify the command (but you can only use the first writing method).
The following is the running situation when I set ENTRYPOINT to ["/bin/sh -c"]:
linux-oj9e:/home/lfly/project /docker # docker run -it t2 /bin/bash
- ##root@4c8549e7ce3e:/# ps ##PID TTY TIME CMD
- 1 ? 00:00:00 sh
- ##9 ? 00:00:00 bash
##19 ? 00:00:00 ps
You can see that the process with PID 1 is running sh, and bash is just a child process of sh,
/bin/bash is only used as the parameter after
. docker tutorial The above is the detailed content of What is the difference between entrypoint and cmd under docker?. For more information, please follow other related articles on the PHP Chinese website!CMD can provide parameters for ENTRYPOINT, and ENTRYPOINT itself can also contain parameters, but you can write the parameters that may need to be changed into CMD and the parameters that do not need to be changed into ENTRYPOINT. For example:
FROM ubuntu:14.10
ENTRYPOINT ["top", "-b"]
CMD ["-c"]

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
