You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Create a build where --mount=type=bind,source=.,dest=/somepath,from=<image> or --mount=type=bind,source=.,dest=/somepath,from=<additional-build-context>
Perform build with --layers
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)
The text was updated successfully, but these errors were encountered:
Description
buildah cache with
--layers
does not work when inRUN
--mount=type=bind
usesimage
oradditional-build-context
as sourceSteps to reproduce the issue:
--mount=type=bind,source=.,dest=/somepath,from=<image>
or--mount=type=bind,source=.,dest=/somepath,from=<additional-build-context>
--layers
--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
orapt list buildah
:Output of
buildah version
:Output of
podman version
if reporting apodman build
issue:Output of
cat /etc/*release
:Output of
uname -a
:Output of
cat /etc/containers/storage.conf
:The text was updated successfully, but these errors were encountered: