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
. 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:
<pre class='brush:php;toolbar:false;'>FROM ubuntu:14.10
ENTRYPOINT ["top", "-b"]
CMD ["-c"]</pre>
Write the parameters that may need to be changed into CMD. Then you can specify parameters in docker run, so that the parameters in CMD (here -c) will be overwritten but those in ENTRYPOINT will not be overwritten.
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!

The ways Docker can simplify development and operation and maintenance processes include: 1) providing a consistent environment to ensure that applications run consistently in different environments; 2) optimizing application deployment through Dockerfile and image building; 3) using DockerCompose to manage multiple services. Docker implements these functions through containerization technology, but during use, you need to pay attention to common problems such as image construction, container startup and network configuration, and improve performance through image optimization and resource management.

The relationship between Docker and Kubernetes is: Docker is used to package applications, and Kubernetes is used to orchestrate and manage containers. 1.Docker simplifies application packaging and distribution through container technology. 2. Kubernetes manages containers to ensure high availability and scalability. They are used in combination to improve application deployment and management efficiency.

Docker solves the problem of consistency in software running in different environments through container technology. Its development history has promoted the evolution of the cloud computing ecosystem from 2013 to the present. Docker uses Linux kernel technology to achieve process isolation and resource limitation, improving the portability of applications. In development and deployment, Docker improves resource utilization and deployment speed, supports DevOps and microservice architectures, but also faces challenges in image management, security and container orchestration.

Docker and virtual machines have their own advantages and disadvantages, and the choice should be based on specific needs. 1.Docker is lightweight and fast, suitable for microservices and CI/CD, fast startup and low resource utilization. 2. Virtual machines provide high isolation and multi-operating system support, but they consume a lot of resources and slow startup.

The core concept of Docker architecture is containers and mirrors: 1. Mirrors are the blueprint of containers, including applications and their dependencies. 2. Containers are running instances of images and are created based on images. 3. The mirror consists of multiple read-only layers, and the writable layer is added when the container is running. 4. Implement resource isolation and management through Linux namespace and control groups.

Docker simplifies the construction, deployment and operation of applications through containerization technology. 1) Docker is an open source platform that uses container technology to package applications and their dependencies to ensure cross-environment consistency. 2) Mirrors and containers are the core of Docker. The mirror is the executable package of the application and the container is the running instance of the image. 3) Basic usage of Docker is like running an Nginx server, and advanced usage is like using DockerCompose to manage multi-container applications. 4) Common errors include image download failure and container startup failure, and debugging skills include viewing logs and checking ports. 5) Performance optimization and best practices include mirror optimization, resource management and security improvement.

The steps to deploy containerized applications using Kubernetes and Docker include: 1. Build a Docker image, define the application image using Dockerfile and push it to DockerHub. 2. Create Deployment and Service in Kubernetes to manage and expose applications. 3. Use HorizontalPodAutoscaler to achieve dynamic scaling. 4. Debug common problems through kubectl command. 5. Optimize performance, define resource limitations and requests, and manage configurations using Helm.

Docker is an open source platform for developing, packaging and running applications, and through containerization technology, solving the consistency of applications in different environments. 1. Build the image: Define the application environment and dependencies through the Dockerfile and build it using the dockerbuild command. 2. Run the container: Use the dockerrun command to start the container from the mirror. 3. Manage containers: manage container life cycle through dockerps, dockerstop, dockerrm and other commands.


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

SecLists
SecLists is the ultimate security tester's companion. It is a collection of various types of lists that are frequently used during security assessments, all in one place. SecLists helps make security testing more efficient and productive by conveniently providing all the lists a security tester might need. List types include usernames, passwords, URLs, fuzzing payloads, sensitive data patterns, web shells, and more. The tester can simply pull this repository onto a new test machine and he will have access to every type of list he needs.

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

ZendStudio 13.5.1 Mac
Powerful PHP integrated development environment

SublimeText3 Chinese version
Chinese version, very easy to use
