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.

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

buildah cache with --layers does not work when in RUN --mount=type=bind uses image or additional-build-context as source #5692

Open
flouthoc opened this issue Aug 18, 2024 · 3 comments · May be fixed by #5693
Assignees

Comments

@flouthoc
Copy link
Collaborator

Description

buildah cache with --layers does not work when in RUN --mount=type=bind uses image or additional-build-context as source

Steps to reproduce the issue:

  1. Create a build where --mount=type=bind,source=.,dest=/somepath,from=<image> or --mount=type=bind,source=.,dest=/somepath,from=<additional-build-context>
  2. Perform build with --layers
  3. Perform build with --layers again.

Describe the results you received:
On second build, entire build must be cached.

Describe the results you expected:
Buildah does not uses cache on the second build.

Output of rpm -q buildah or apt list buildah:

(paste your output here)

Output of buildah version:

(paste your output here)

Output of podman version if reporting a podman build issue:

(paste your output here)

Output of cat /etc/*release:

(paste your output here)

Output of uname -a:

(paste your output here)

Output of cat /etc/containers/storage.conf:

(paste your output here)
@flouthoc flouthoc self-assigned this Aug 18, 2024
@flouthoc
Copy link
Collaborator Author

Found this issue while working on #5691

Copy link

A friendly reminder that this issue had no activity for 30 days.

@flouthoc
Copy link
Collaborator Author

This is not stale, waiting on review here: #5693 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant