Tonis Tiigi 6ed70f8651 executor: restore mount points removed for rootless ...

The rootless spec conversion removes the /sys mount, so the runtime never
creates its mount point in the rootfs. A rootful build gets that empty
directory, which meant the same LLB left different mount points behind
depending on whether the worker was rootless.

Recreate the mount points of the removed mounts after the container has
exited, rather than cleaning them up from the rootful result, which would
change existing output and need a compatibility version bump. Creating
them up front would instead turn a mount point that the image does not
ship into a directory the build can write to. Nested destinations are
skipped: the runtime creates those inside the parent mount, where they
never reach the rootfs.

Fixes #6686

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>

2026-08-13 16:04:16 +03:00

..

executor_test.go

Refactor error handling to use errors.New for consistency

2026-08-07 10:13:54 +02:00

executor_unix.go

executor: restore mount points removed for rootless

2026-08-13 16:04:16 +03:00

executor_windows.go

Rename isolated to hypervIsolation

2025-09-16 23:59:37 +08:00

executor.go

executor: restore mount points removed for rootless

2026-08-13 16:04:16 +03:00