-
Notifications
You must be signed in to change notification settings - Fork 74
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
How best to use with multi-stage? #129
Comments
I think this could be doable by mounting the same host path to both container image builds:
I agree it would be lovely to get native support in bender for multi-stage builds. |
Oh, that makes sense! That's a perfect workaround for now. |
okay, so let's treat this issue as a lack of documentation |
Just found this after leaving a comment on Tomáš's blog. Here's a different way I found to do this:
This will put the source image's local filesystem path in the variable |
Maybe a mode where each play gets treated as a separate image (or layer)? |
However, currently mounting using overlay in rootless mode is not supported. when $ buildah mount pulsar-all-temp
cannot mount using driver overlay in rootless mode. You need to run it in a `buildah unshare` session |
Love the tool idea. I am wondering how best to use ansible-bender with multi-stage builds.
In the Docker world, I can leave build dependencies behind by using two images:
With ansible-bender, I can see how to make the first image but not the second.
What do you think?
The text was updated successfully, but these errors were encountered: