We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The --layers option is useful in buildah when given a persistent disk, but not useful in CI systems where the disk is discarded after each job
Since we've verified this option allows caching to work in the self-hosted buildah runner we should add an input for it
To keep with buildah behaviour, it should be false by default.
In addition, it may make sense to set export BUILDAH_LAYERS=true into the runner.
export BUILDAH_LAYERS=true
The text was updated successfully, but these errors were encountered:
I am adding BUILDAH_LAYERS=true to the buildah runner dockerfile, but if --layers=false is passed to this action then the env var will get overridden.
BUILDAH_LAYERS=true
--layers=false
So if layers is not set, do not pass --layers at all, to leave it up to the environment.
layers
--layers
Sorry, something went wrong.
Add BUILDAH_LAYERS=true to buildah dockerfile
8d91448
redhat-actions/buildah-build#42 Signed-off-by: Tim Etchells <tetchel@gmail.com>
Okay 👍
divyansh42
No branches or pull requests
The --layers option is useful in buildah when given a persistent disk, but not useful in CI systems where the disk is discarded after each job
Since we've verified this option allows caching to work in the self-hosted buildah runner we should add an input for it
To keep with buildah behaviour, it should be false by default.
In addition, it may make sense to set
export BUILDAH_LAYERS=true
into the runner.The text was updated successfully, but these errors were encountered: