Docker's build operation is based on cache by default, that is, after you modify the Dockerfile, the build task will quickly skipyour previous successful steps, and all operations after the step you modified will be re-run. If you want each build not to be based on the previous cache, add the --no-cache=true parameter to the build command Also see: Dockerfile best practices
Normally speaking, there is no need to re-run the previous steps when rebuilding. Just 从失败的那条RUN开头的命令开始接着处理;
It is recommended that you split multiple commands into independent RUN commands; ensure that you do not need to re-run the previous RUN command each time;
Docker's build operation is based on cache by default, that is, after you modify the Dockerfile, the build task will quickly skipyour previous successful steps, and all operations after the step you modified will be re-run.
If you want each build not to be based on the previous cache, add the --no-cache=true parameter to the build command
Also see:
Dockerfile best practices
Normally speaking, there is no need to re-run the previous steps when rebuilding. Just
从失败的那条RUN开头的命令开始接着处理
;It is recommended that you split multiple commands into independent RUN commands; ensure that you do not need to re-run the previous RUN command each time;