Buildpacks not getting detected through uri #257
Replies: 3 comments 1 reply
-
I'm not sure why you'd see a difference here based on the info presented. I would suggest pointing to images, but that's not a requirement. I suggest that because images are a lot more precise than a folder. The folder contents can change, whereas the image cannot change (at least not without causing the hash to change). |
Beta Was this translation helpful? Give feedback.
-
@dmikusa , yeah the image is participating correctly, but the uri (folder) is not participating. |
Beta Was this translation helpful? Give feedback.
-
Okay @dmikusa . Will share the logs for it |
Beta Was this translation helpful? Give feedback.
-
[[buildpacks]]
id = "paketo-buildpacks/web-servers"
version = "0.17.2"
uri = "../web-server-buildpack"
When I pass my buildpacks in the builder like this, it is not getting detected (not participating).
[[buildpacks]]
uri = "docker://xyz/paketo-buildpacks/web-servers:0.17.2"
version = "0.17.2"
But when I pass my buildpacks like this , in the builder , it is participating.
This case would be useful , if I have buildpacks of different versions needing to be supported in the same builder image.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions