Docker-commit

本文详细介绍了如何使用Docker的Commit命令来定制和保存修改后的镜像,探讨了这一操作对于镜像管理和分发的影响,同时强调了在实际应用中应谨慎使用Commit的原因。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

  1. 之前理解了镜像是分层构成后,并且我们修改了我们的nginx的index页面,如果想把这个nginx镜像保存下来供其他人使用,那么我们就需要进行“保护现场”,这也是commit命令的作用
  2. 我们先来看一下我的机子上有那些容器

    [qidai@qidai-pc ~]$ docker ps -a
    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                    PORTS               NAMES
    b5c597a4f124        nginx               "nginx -g 'daemon of…"   26 hours ago        Exited (0) 23 hours ago                       webnginx
    76110444b847        91dadee7afee        "docker-entrypoint.s…"   3 days ago          Exited (0) 2 days ago                         my-test-mysql
  3. 我们更改后webnginx后现在进行保存

    [qidai@qidai-pc ~]$ docker commit --author "qidai" --message "change webnginx index.html" webnginx nginx:v1
    sha256:ca9ac899159eefe41cf30771cc2f4e23db967d6e2f3d0725226495296b69cb76
    • --author:指定作者
    • --message:备注信息
    • 再之后是指定保存的哪个镜像,然后紧接着是保存后的名字和版本
  4. 保存后我们在来看一下本地image

    [qidai@qidai-pc ~]$ docker images
    REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
    nginx               v1                  ca9ac899159e        3 minutes ago       109MB
    nginx               latest              881bd08c0b08        4 days ago          109MB
    ubuntu              latest              47b19964fb50        4 weeks ago         88.1MB
    centos              latest              1e1148e4cc2c        3 months ago        202MB
  5. 会多出来一个nginx:v1镜像,我们把它run起来

    [qidai@qidai-pc ~]$ docker run --rm -d -p 80:80 nginx:v1
    1c494ae39be7666f1c3249054b5657b24bebe192009761d1063e424f601bb672
    [qidai@qidai-pc ~]$ docker ps
    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                NAMES
    1c494ae39be7        nginx:v1            "nginx -g 'daemon of…"   9 seconds ago       Up 7 seconds        0.0.0.0:80->80/tcp   recursing_zhukovsky
  6. 这个时候再次访问 localhost就会直接出现我们修改后的index页面信息
  7. 虽然commit可以为我们定制镜像,但还是要 慎用 原因如下

    • commit后其实就是将nginx与base image打到一个包中了,那么只有你自己知道你的镜像发生了什么,而对于别人来说完全是一个黑箱
    • 之前提到的分层概念,我们nginx修改只修改了当前层,如果进行commit,别人使用你的这个镜像的时候就会在nginx层在继续添加自己的层,会使得镜像越来越臃肿
    • 我们也注意到启动nginx服务并不是只更改了index页面,而是对应的cache都会发生改变,如果在发生编译安装将会安装更多依赖库,commit后让他们成为了一体,这样也会使得镜像更加臃肿
PS C:\Users\34537\dify\docker> docker compose up -d [+] Running 12/12 ✔ Network docker_default Created 0.1s ✔ Network docker_ssrf_proxy_network Created 0.0s ✔ Container docker-weaviate-1 Started 1.3s ✔ Container docker-sandbox-1 Started 1.5s ✔ Container docker-db-1 Healthy 4.0s ✔ Container docker-redis-1 Started 1.4s ✔ Container docker-ssrf_proxy-1 Started 1.5s ✔ Container docker-web-1 Started 1.5s ✔ Container docker-api-1 Started 4.7s ✔ Container docker-worker-1 Started 4.6s ✔ Container docker-plugin_daemon-1 Started 4.4s ✔ Container docker-nginx-1 Started 4.9s PS C:\Users\34537\dify\docker> docker compose ps NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS docker-api-1 langgenius/dify-api:1.5.1 "/bin/bash /entrypoi…" api 14 seconds ago Up 9 seconds 5001/tcp docker-db-1 postgres:15-alpine "docker-entrypoint.s…" db 14 seconds ago Up 12 seconds (healthy) 5432/tcp docker-nginx-1 nginx:latest "sh -c 'cp /docker-e…" nginx 14 seconds ago Up 4 seconds 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp docker-plugin_daemon-1 langgenius/dify-plugin-daemon:0.1.3-local "/bin/bash -c /app/e…" plugin_daemon 14 seconds ago Up 9 seconds 0.0.0.0:5003->5003/tcp docker-redis-1 redis:6-alpine "docker-entrypoint.s…" redis 14 seconds ago Up 13 seconds (health: starting) 6379/tcp docker-sandbox-1 langgenius/dify-sandbox:0.2.12 "/main" sandbox 14 seconds ago Up 13 seconds (health: starting) docker-ssrf_proxy-1 ubuntu/squid:latest "sh -c 'cp /docker-e…" ssrf_proxy 14 seconds ago Up 12 seconds 3128/tcp docker-weaviate-1 semitechnologies/weaviate:1.19.0 "/bin/weaviate --hos…" weaviate 14 seconds ago Up 13 seconds docker-web-1 langgenius/dify-web:1.5.1 "/bin/sh ./entrypoin…" web 14 seconds ago Restarting (0) 3 seconds ago docker-worker-1 langgenius/dify-api:1.5.1 "/bin/bash /entrypoi…" worker 14 seconds ago Up 9 seconds 5001/tcp PS C:\Users\34537\dify\docker> docker compose ps NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS docker-api-1 langgenius/dify-api:1.5.1 "/bin/bash /entrypoi…" api 2 minutes ago Up 2 minutes 5001/tcp docker-db-1 postgres:15-alpine "docker-entrypoint.s…" db 2 minutes ago Up 2 minutes (healthy) 5432/tcp docker-nginx-1 nginx:latest "sh -c 'cp /docker-e…" nginx 2 minutes ago Restarting (1) 10 seconds ago docker-plugin_daemon-1 langgenius/dify-plugin-daemon:0.1.3-local "/bin/bash -c /app/e…" plugin_daemon 2 minutes ago Up 2 minutes 0.0.0.0:5003->5003/tcp docker-redis-1 redis:6-alpine "docker-entrypoint.s…" redis 2 minutes ago Up 2 minutes (healthy) 6379/tcp docker-sandbox-1 langgenius/dify-sandbox:0.2.12 "/main" sandbox 2 minutes ago Up 2 minutes (unhealthy) docker-ssrf_proxy-1 ubuntu/squid:latest "sh -c 'cp /docker-e…" ssrf_proxy 2 minutes ago Up 2 minutes 3128/tcp docker-weaviate-1 semitechnologies/weaviate:1.19.0 "/bin/weaviate --hos…" weaviate 2 minutes ago Up 2 minutes docker-web-1 langgenius/dify-web:1.5.1 "/bin/sh ./entrypoin…" web 2 minutes ago Restarting (0) 56 seconds ago docker-worker-1 langgenius/dify-api:1.5.1 "/bin/bash /entrypoi…" worker 2 minutes ago Up 2 minutes 5001/tcp PS C:\Users\34537\dify\docker> docker logs docker-web-1 PS C:\Users\34537\dify\docker> docker logs --tail 100 docker-web-1 PS C:\Users\34537\dify\docker> docker logs --previous docker-web-1 unknown flag: --previous See 'docker logs --help'. 其中docker-web-1一直在Restarting,并且关于web日志一直没反应,该怎么办(说中文)
最新发布
07-09
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值