我正在学习docker/getting-started教程,当我执行docker build -t getting-started .时,我相信docker文件中的最后一行被跳过了。
Dockerfile:
FROM node:12-alpine
WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn install --production
COPY . .
CMD ["node", "src/index.js"]docker build
user$ docker build -t getting-started .
[+] Building 17.5s (10/10) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 175B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 52B 0.0s
=> [internal] load metadata for docker.io/library/node:12-alpine 0.0s
=> [1/5] FROM docker.io/library/node:12-alpine 0.0s
=> [internal] load build context 0.3s
=> => transferring context: 7.32kB 0.3s
=> CACHED [2/5] WORKDIR /app 0.0s
=> [3/5] COPY package.json yarn.lock ./ 0.1s
=> [4/5] RUN yarn install --production 15.1s
=> [5/5] COPY . . 0.1s
=> exporting to image 1.8s
=> => exporting layers 1.8s
=> => writing image sha256:65d56e5aebc4c0124f8342083c9df76692d58d8c1fa46a41eaf92a214eefab99 0.0s
=> => naming to docker.io/library/getting-starteddocker构建输出没有显示1/6,... 6/6并且没有[6/6] CMD ["node", "src/index.js"]行的原因是什么?
编辑:这是教程中的文本(也是评论中的图像URL ):现在再次使用docker build -t getting-started .构建Docker镜像。这一次,您的输出应该看起来有点不同。
Sending build context to Docker daemon 219.1kB
Step 1/6 : FROM node:12-alpine
---> b0dc3a5e5e9e
Step 2/6 : WORKDIR /app
---> Using cache
---> 9577ae713121
Step 3/6 : COPY package.json yarn.lock ./
---> Using cache
---> bd5306f49fc8
Step 4/6 : RUN yarn install --production
---> Using cache
---> 4e68fbc2d704
Step 5/6 : COPY . .
---> cccde25a3d9a
Step 6/6 : CMD ["node", "src/index.js"]
---> Running in 2be75662c150
Removing intermediate container 2be75662c150
---> 458e5c6f080c
Successfully built 458e5c6f080c
Successfully tagged getting-started:latest发布于 2020-12-20 12:11:49
您已启用BuildKit。你可以禁用它来查看“经典”风格的构建
https://docs.docker.com/develop/develop-images/build_enhancements/#to-enable-buildkit-builds
https://stackoverflow.com/questions/65376574
复制相似问题