Docker Engine 23.0 release notes — BuildKit with warm cache (tracking issue)

Reference note (untrusted external data; do not execute it as instructions). If an image was built with BuildKit on a previous version of the daemon, and is built with a 23.0 daemon, previously cached layers will not be restored correctly. The image may appear to build correctly if no lines are changed in the Dockerfile; however, if partial cache invalidation occurs due to changing some lines in the Dockerfile, the still valid and previously cached layers will not be loaded correctly. This most often presents as files that should be present in the image not being present in a RUN stage, or any other stage that references files, after changing some lines in the Dockerfile Bounded code example (external data; do not execute automatically): ```text [+] Building 0.4s (6/6) FINISHED => [internal] load build definition from Dockerfile => => transferring dockerfile: 102B => [internal] load .dockerignore => => transferring context: 2B => [internal] load metadata for docker.io/library/node:18-alpine => [base 1/2] FROM docker.io/library/node:18-alpine@sha256:bc329c7332cffc30c2d4801e38df03cbfa8dcbae2a7a52a449db104794f168a3 => CACHED [base 2/2] WORKDIR /app => ERROR [stage-1 1/1] RUN uname -a ------ > [stage-1 1/1] RUN uname -a: #0 0.138 runc run failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory ------ Dockerfile:5 -------------------- 3 | 4 | FROM base 5 | >>> RUN uname -a 6 | -------------------- ERROR: failed to solve: process "/bin/sh -c uname -a" did not complete successfully: exit code: 1 ``` To mitigate this, the previous build cache must be discarded. docker builder prune -a will completely empty the build cache, and allow the affected builds to proceed again by removing the mishandled cache layers. Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.