-
Notifications
You must be signed in to change notification settings - Fork 12
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
CNB lifecycle can't restore cached layer for go-mod #6
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/168351842 The labels on this github issue will be updated when the story is started. |
Hi @bstick12, This appears to be an issue with the CNB lifecycle. It should be possible to restore layers regardless of their permissions. The lifecycle should implement the equivalent of Would you mind opening an issue here? |
Thanks @sclevine. I've opened buildpacks/lifecycle#177 |
@bstick12 Closing this issue in favor of buildpack/lifecycle#177. |
What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running
cf curl /v2/info && cf version
?N/A - Was testing the
go-mod
using kpackWhat version of the buildpack you are using?
[email protected]
If you were attempting to accomplish a task, what was it you were attempting to do?
Rebuild an image using kpack where caching was enabled
What did you expect to happen?
The image would be re-built using the cached layers
What was the actual behavior?
The lifecycle of CNB fails at
restore
as the layer tar can be uncompressedThe previous layer is correctly used from cache
The problem lies with the go module package paths. The package directories are not writeable. Apparently this is by design as discussed in golang/go#27161 and golang/go#27455 (comment)
This permission is preserved in the tarball
Since without a change to the tar or untaring process for this buildpack the caching process will break. Would be possible to disable caching.
Can you provide a sample app?
The behaviour should be the same for any go application that use go modules.
Please confirm where necessary:
The text was updated successfully, but these errors were encountered: