Question

如此处所述https://docs.docker.com/compose/gettingstarted/#step-7-update-the-application，如果我在该 docker 的 volumes 中安装带有源代码的文件夹，我应该立即看到我的更改...

然而，这是我的docker-compose：

version: '3'

services: 
    database:
        ...

    engine:
        build: ./name
        restart: always
        volumes: 
            - .:/name-code
            - ./name/config-examples:/config
        ports: 
            - 8080:8080
        depends_on: 
            - database
        environment: 
            - TZ=Europe/Rome
            ...

    grafana:
        ...

正如你所看到的，我正在安装 .:/name-code...所以只要我改变了这个目录中的代码，我就会看到 docker 用新的 JAR 重新启动（我正在开发一个 Spring 启动应用程序)...但是这并没有发生，事实上我的本地罐子看起来像这样：

-rw-r--r--    1 user     staff     43171359 Jun  1 12:35 project.jar

但是docker中的jar如下：

-rw-r--r--    1 root     root      43171269 May 31 19:52 app.jar

（刚刚重命名），但正如您所见，上次更新非常不同，实际上没有导入更新

日志：

docker-compose --verbose build           
compose.config.config.find: Using configuration files: ./docker-compose.yml
compose.cli.docker_client.get_client: docker-compose version 1.29.1, build c34c88b2
docker-py version: 5.0.0
CPython version: 3.9.0
OpenSSL version: OpenSSL 1.1.1h  22 Sep 2020
compose.cli.docker_client.get_client: Docker base_url: http+docker://localhost
compose.cli.docker_client.get_client: Docker version: Platform={'Name': 'Docker Engine - Community'}, Components=[{'Name': 'Engine', 'Version': '20.10.6', 'Details': {'ApiVersion': '1.41', 'Arch': 'amd64', 'BuildTime': '2021-04-09T22:44:56.000000000+00:00', 'Experimental': 'false', 'GitCommit': '8728dd2', 'GoVersion': 'go1.13.15', 'KernelVersion': '5.10.25-linuxkit', 'MinAPIVersion': '1.12', 'Os': 'linux'}}, {'Name': 'containerd', 'Version': '1.4.4', 'Details': {'GitCommit': '05f951a3781f4f2c1911b05e61c160e9c30eaa8e'}}, {'Name': 'runc', 'Version': '1.0.0-rc93', 'Details': {'GitCommit': '12644e614e25b05da6fd08a38ffa0cfe1903fdec'}}, {'Name': 'docker-init', 'Version': '0.19.0', 'Details': {'GitCommit': 'de40ad0'}}], Version=20.10.6, ApiVersion=1.41, MinAPIVersion=1.12, GitCommit=8728dd2, GoVersion=go1.13.15, Os=linux, Arch=amd64, KernelVersion=5.10.25-linuxkit, BuildTime=2021-04-09T22:44:56.000000000+00:00
compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- ('codice_default')
compose.cli.verbose_proxy.proxy_callable: docker inspect_network -> {'Attachable': False,
 'ConfigFrom': {'Network': ''},
 'ConfigOnly': False,
 'Containers': {},
 'Created': '2021-06-01T10:31:25.2768986Z',
 'Driver': 'bridge',
 'EnableIPv6': False,
 'IPAM': {'Config': [{'Gateway': '172.31.0.1', 'Subnet': '172.31.0.0/16'}],
          'Driver': 'default',
          'Options': None},
...
compose.project.build: database uses an image, skipping
compose.project.build: grafana uses an image, skipping
compose.service.build: Building engine
[+] Building 0.3s (8/8) FINISHED                                                                                                                                                               
 => [internal] load build definition from Dockerfile                                                                                                                                      0.0s
 => => transferring dockerfile: 37B                                                                                                                                                       0.0s
 => [internal] load .dockerignore                                                                                                                                                         0.0s
 => => transferring context: 2B                                                                                                                                                           0.0s
 => [internal] load metadata for docker.io/adoptopenjdk/openjdk11:jdk-11.0.11_9-alpine-slim                                                                                               0.0s
 => [1/3] FROM docker.io/adoptopenjdk/openjdk11:jdk-11.0.11_9-alpine-slim                                                                                                                 0.0s
 => [internal] load build context                                                                                                                                                         0.0s
 => => transferring context: 1.43kB                                                                                                                                                       0.0s
 => CACHED [2/3] COPY target/*.jar app.jar                                                                                                                                                0.0s
 => [3/3] COPY config-examples /app/config                                                                                                                                                0.0s
 => exporting to image                                                                                                                                                                    0.1s
 => => exporting layers                                                                                                                                                                   0.0s
 => => writing image sha256:7162be9dfe5c15feedd12d19a5985a0f619e623eb69e949283c6e2d66442f533                                                                                              0.0s
 => => naming to docker.io/library/codice_engine                                                                                                                                          0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them

Dockerfile 服务的 engine 如下：

FROM adoptopenjdk/openjdk11:jdk-11.0.11_9-alpine-slim
ARG JAR_FILE=target/*.jar
COPY ${JAR_FILE} app.jar
COPY config-examples /app/config

CMD ["java","-jar","/app.jar"]

Answer 1

我又看了你的帖子，误解在于.:/name-code 是卷挂载点，它不是由 docker-compose 构建的 docker 镜像的一部分，所以更改其内容不会强制 docker 重建映像。否则，可以从容器访问新内容。

因此，您可以看到 CACHED [2/3] COPY target/*.jar app.jar 是从缓存图层中检索的。

在我看来，解决方案是编写一个自定义的 Dockerfile，它显式添加 jar，如此处所示 https://docs.docker.com/compose/compose-file/compose-file-v3/#dockerfile 。因此，每次 jar 更改时，映像都会按照您的预期重建。

问候。

代码更改时 Docker 不会重新启动

1 个答案: