如何让 docker build 的时候,不要联网更新基础镜像?-灵析社区

Ufoooo4U

FROM python:3.11.5-bookworm RUN echo "deb http://mirrors.aliyun.com/debian/ bookworm main non-free contrib" > /etc/apt/sources.list 对于 `python:3.11.5-bookworm` 这个镜像 每次运行 `docker build -t "ponponon/svddb_api:2023.09.08.1" .` 好像都回去检查 dockerhub 上 `python:3.11.5-bookworm` 是否要更新? 但是因为连接 dockerhub 挺慢的,我希望本地已经有 `python:3.11.5-bookworm` 了就不要去联网更新 `python:3.11.5-bookworm` 了 ╰─➤ docker images | grep python python 3.10.10-bullseye 2b8b079d7548 5 months ago 912MB 从上面可以看到,我本地已经有 `python:3.11.5-bookworm` 了 ─➤ make build docker build -t "ponponon/svddb_api:2023.09.08.1" . [+] Building 256.2s (4/18) docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 914B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2.31kB 0.0s => [internal] load metadata for docker.io/library/python:3.11.5-bookworm 36.3s => [internal] load build context 0.1s => => transferring context: 176.86kB 0.1s => [ 1/14] FROM docker.io/library/python:3.11.5-bookworm@sha256:3d10a95a05674b7e42ac53267774880b255949e5e2aed 219.9s => => resolve docker.io/library/python:3.11.5-bookworm@sha256:3d10a95a05674b7e42ac53267774880b255949e5e2aed9be5 0.0s => => sha256:22c957c35e37bdd688c2bdda50dc72612477d6c9c393802163b14d197a568bff 7.53kB / 7.53kB 0.0s => => sha256:012c0b3e998c1a0c0bedcf712eaaafb188580529dd026a04aa1ce13fdb39e42b 49.56MB / 49.56MB 80.9s => => sha256:00046d1e755ea94fa55a700ca9a10597e4fac7c47be19d970a359b0267a51fbf 24.03MB / 24.03MB 43.2s => => sha256:9f13f5a53d118643c1f1ff294867c09f224d00edca21f56caa71c2321f8ca004 64.11MB / 64.11MB 69.5s => => sha256:3d10a95a05674b7e42ac53267774880b255949e5e2aed9be590143df33f95c64 1.65kB / 1.65kB 0.0s => => sha256:8a164692c20c8f51986d25c16caa6bf03bde14e4b6e6a4c06b5437d5620cc96c 2.01kB / 2.01kB 0.0s => => sha256:e13e76ad6279c3d69aa6842a935288c7db66878ec3b7815edd3bb34647bd7ed0 137.36MB / 210.99MB 219.9s => => sha256:ad4c837a72f8d2d63d64bf7f9d7c43fe9e67f3d82af7ac47e977a06b95ff7b3a 6.39MB / 6.39MB 92.7s => => extracting sha256:012c0b3e998c1a0c0bedcf712eaaafb188580529dd026a04aa1ce13fdb39e42b 0.6s => => sha256:0f546edb7ae0f7fecbac92a156849e2479dbf591ed0be9ac68e873da28c2a7a7 19.78MB / 19.78MB 120.8s => => extracting sha256:00046d1e755ea94fa55a700ca9a10597e4fac7c47be19d970a359b0267a51fbf 0.2s => => extracting sha256:9f13f5a53d118643c1f1ff294867c09f224d00edca21f56caa71c2321f8ca004 0.8s => => sha256:e2f1160974087f047a90d64ce50bd95d279c89309f32caeaa0b3503c253cab45 244B / 244B 107.9s => => sha256:a0d3c67a6b6b0b67a9e4735c18ae78ca68e2252e0bed7e6fc3912dd5e0e8f042 3.11MB / 3.11MB 124.2s * * * 这部分耗时挺久的 ![图片.png](https://wmprod.oss-cn-shanghai.aliyuncs.com/images/20250105/8f1969d4664b0f21e178aacf77082ba9.png) * * * 好像可能是乌龙 之前没有显性执行过 docker pull python:3.11.5-bookworm

阅读量:361

点赞量:10

问AI
除非你显式指定了 "--pull" 参数,否则 "docker build" 只会用本地的镜像,不会联网检查更新的(前提是你本地确实有这个 tag)。 你这里的“好像”是根据什么判断出来的?