CMD和ENTRYPOINT区别

最新推荐文章于 2024-12-16 22:58:06 发布

码农娟

最新推荐文章于 2024-12-16 22:58:06 发布

阅读量593

点赞数

分类专栏： Docker 文章标签： docker

本文链接：https://blog.csdn.net/weixin_40750633/article/details/122929176

版权

Docker 专栏收录该内容

22 篇文章 7 订阅

订阅专栏

本文通过实例演示了Dockerfile中CMD和ENTRYPOINT的区别。CMD指定的命令会被运行时的参数替换，而ENTRYPOINT指定的命令会作为基础命令，运行时的参数将作为其附加参数。当使用CMD时，尝试追加-l命令导致错误，因为-l不是一个有效的命令。而使用ENTRYPOINT时，-l作为ls命令的参数正常工作，展示了命令的拼接行为。

摘要由CSDN通过智能技术生成

CMD         指定这个容器启动的时候要运行的命令，只有最后一个会生效，可被替代 
ENTRYPOINT  指定这个容器启动的时候要运行的命令，可以追加命令

测试CMD

#编写dockfile 文件
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# vim dockerfile-cmd-test
FROM centos
CMD ["ls","-a"]
#构建镜像
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker build -f dockerfile-cmd-test -t cmdtest .

#run运行，发现ls-a命令生效
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker run 45fb7b0b22fb
.
..
.dockerenv
bin
dev
etc
home
lib
lib64
.
.

# 想追加一个命令  ls  -al
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker run 45fb7b0b22fb -l
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "-l": executable file not found in $PATH: unknown.

#cmd的情况下，-l 替换了CMD ["ls","-a"]命令，-l不是命令，所以报错

测试ENTRYPOINT

[root@iZwz9geewjuo2sogidqn50Z dockerfile]# vim dockerfile-cmd-entrypoint
FROM centos
ENTRYPOINT ["ls","-a"]

[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker build -f dockerfile-cmd-entrypoint  -t entrypoint .
Sending build context to Docker daemon   21.5kB
Step 1/2 : FROM centos
 ---> 5d0da3dc9764
Step 2/2 : ENTRYPOINT ["ls","-a"]
 ---> Running in b2303d65eb10
Removing intermediate container b2303d65eb10
 ---> bb7442af8578
Successfully built bb7442af8578
Successfully tagged entrypoint:latest
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker run bb7442af8578
.
..
.dockerenv
bin
dev
etc
home
lib
lib64
lost+found
media
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var

#追加命令，是直接拼接在ENTRYPOINT 命令的后面
[root@iZwz9geewjuo2sogidqn50Z dockerfile]# docker run bb7442af8578 -l
total 56
drwxr-xr-x   1 root root 4096 Jan 19 09:21 .
drwxr-xr-x   1 root root 4096 Jan 19 09:21 ..
-rwxr-xr-x   1 root root    0 Jan 19 09:21 .dockerenv
lrwxrwxrwx   1 root root    7 Nov  3  2020 bin -> usr/bin
drwxr-xr-x   5 root root  340 Jan 19 09:21 dev
drwxr-xr-x   1 root root 4096 Jan 19 09:21 etc
drwxr-xr-x   2 root root 4096 Nov  3  2020 home
lrwxrwxrwx   1 root root    7 Nov  3  2020 lib -> usr/lib
lrwxrwxrwx   1 root root    9 Nov  3  2020 lib64 -> usr/lib64
drwx------   2 root root 4096 Sep 15 14:17 lost+found
drwxr-xr-x   2 root root 4096 Nov  3  2020 media
drwxr-xr-x   2 root root 4096 Nov  3  2020 mnt
drwxr-xr-x   2 root root 4096 Nov  3  2020 opt
dr-xr-xr-x 198 root root    0 Jan 19 09:21 proc
dr-xr-x---   2 root root 4096 Sep 15 14:17 root
drwxr-xr-x  11 root root 4096 Sep 15 14:17 run
lrwxrwxrwx   1 root root    8 Nov  3  2020 sbin -> usr/sbin
drwxr-xr-x   2 root root 4096 Nov  3  2020 srv
dr-xr-xr-x  13 root root    0 Jan 19 09:21 sys
drwxrwxrwt   7 root root 4096 Sep 15 14:17 tmp
drwxr-xr-x  12 root root 4096 Sep 15 14:17 usr
drwxr-xr-x  20 root root 4096 Sep 15 14:17 var