-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
broken build because invalid mount type "cache" in RUN #12062
Comments
@sn3d This was recently merged in buildah. You will find this in newer versions of podman as soon as buildah is vendored in. Closing this one. Please re-open if something is not resolved. |
@flouthoc Thanks for clarification. Make sense. This brings me to another question but I'll ask in Discussions. Thanks a lot. |
@sn3d Sure or you can continue discussion on this issue or open a new issue on buildah or a Discussions. Whatever you feel is the best place. |
Hi, is there a new version out supporting this? |
3.4.2 is the latest version. |
The buildah dependency is only updated for 4.0.0 any plan to also bump it for the 3.x branch? |
We do not plan any further releases from the v3.x branches. Podman v4.0 should release next Tuesday. |
Alright thanks for the quick reply ❤️❤️ |
/kind bug
Description
Podman build failed when Dockerfile contains RUN --mount=cache
Steps to reproduce the issue:
podman build .
Describe the results you received:
Describe the results you expected:
Maybe
podman build
should continue without cache. Rather no-cache than broken build.Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: