-
Notifications
You must be signed in to change notification settings - Fork 817
Buildah does not pull from cache when building a container in a CI/CD pipeline #6121
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
Comments
Hi @vigno88 , If you could share the debug logs in the CI/CD environment |
Yes for sure. The following are two runs of buildah build with the same command. Knowing for sure that the layer exist, why did buildah didn't pull it in the second run ?
|
A friendly reminder that this issue had no activity for 30 days. |
In an attempt to cache intermediate layer when building images, I've first started to test on my local PC with such a command:
This runs as expected locally, buildah reuses layer from the .../cache repo and the build is completed using the layers instead of rebuilding each layer every time.
When doing the same in a CI/CD pipeline (running in a pod on k8s), I was getting different digest for each layer in the cache so i've introduced the
--timestamp 0
and--omit-history
argument and this fixed my initial issue. I was able to get the same digest for the same layer each build, for example:Each of my build results in the same step having the same digest, but it won't pull the cache layer during build. Even though it exists in the repository and it does pull it when running on my PC.
What could cause buildah to skip the pulling of the layer only in my CI/CD environment.
Thanks
The text was updated successfully, but these errors were encountered: