-
Notifications
You must be signed in to change notification settings - Fork 286
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
Stack fix & create new volume cache for kaniko instead of re-using build cache #1789
Conversation
This removes the unnecessary restriction that the build cache must be a volume cache in order to use extensions. Signed-off-by: Natalie Arellano <[email protected]>
if c.Build.Format == CacheBind { | ||
if resolvedPath, err = filepath.Abs(c.Build.Source); err != nil { | ||
return errors.Wrap(err, "resolve absolute path") | ||
} | ||
c.Build.Source = filepath.Join(resolvedPath, "build-cache") | ||
} | ||
if c.Launch.Format == CacheBind { | ||
if resolvedPath, err = filepath.Abs(c.Launch.Source); err != nil { | ||
return errors.Wrap(err, "resolve absolute path") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally unrelated change... I can pull it out of this PR if desired. Looking through the code it seems the current implementation unnecessarily skips resolving the launch cache when the build cache is a bind.
I can see you have the following error message during the test execution:
I have something similar in my flattened fixes PR, do you have any thoughts on root cause for that? |
Thanks for the review @jjbustamante! This looks to be an issue in the lifecycle - I put up buildpacks/lifecycle#1117 |
Signed-off-by: Joe Kimmel <[email protected]>
…eparellano) Signed-off-by: Joe Kimmel <[email protected]>
I've confirmed manually that lifecycle built from |
only add the stack arg to lifecycle for older platform APIs
Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
The fixture changed, so its SHA changed Signed-off-by: Natalie Arellano <[email protected]>
…m api Without this change, users would be required to upgrade their lifecycle to 0.17.0 when consuming pack 0.30.0 if using build image extension, as the restorer would fail to write to the /kaniko directory. Signed-off-by: Natalie Arellano <[email protected]>
Signed-off-by: Natalie Arellano <[email protected]>
This removes the unnecessary restriction that the build cache must be a volume cache in order to use extensions.