Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

exec: fix pruning cache mounts with parent ref on no-cache #5306

Merged
merged 1 commit into from
Sep 9, 2024
Merged

exec: fix pruning cache mounts with parent ref on no-cache #5306

merged 1 commit into from
Sep 9, 2024

Commits on Sep 6, 2024

  1. exec: fix pruning cache mounts with parent ref on no-cache 

    On a build with no-cache, cache mounts were not pruned correctly
if the mount was on top of another ref. This also appeared in
Dockerfile when mode/uid/gid was set because implicit parent
ref is created in these cases in order to change the permissions
of a subdir that is used as a cache mount base.

Because it is not possible to know ahead of time what ref
will become the parent of cache mount during build, all cache
mounts matching the ID that have a parent will be pruned.

Signed-off-by: Tonis Tiigi <[email protected]>
    @tonistiigi
    tonistiigi committed Sep 6, 2024
    Configuration menu
    Copy the full SHA
    610affa View commit details
    Browse the repository at this point in the history