-
Notifications
You must be signed in to change notification settings - Fork 112
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
"Creator" with Buildpack usage #959
Comments
Hi @anoopvlcy. One doubt, are you planning to build your images using a different tool than pack cli? I asked because I think pack is already using the creator if your builder is trusted(see this) The creator makes life easier for platform implementors because they do not have to call every phase one by one. Pack (as a platform) is already handling that for you as. |
As @jjbustamante mentions you can provide |
hi @natalieparellano , @jjbustamante Thanks for quick response. I'm exploring "creator" because, currently Pack Docker image doesn't support Gitlab. Please refer ticket. Please let me know is there any alternatives or workaround till "prepare" binary available for use. So that I can try "creator" in Gitlab. |
@anoopvlcy commented on the other ticket; I am pretty sure you can get |
Thanks. I replied in buildpacks/pack#1554 |
Closing this issue as it seems covered by the pack issue; feel free to reopen if I'm mistaken. |
Description
Looking for some example for using buildpack option with "/cnb/lifecycle/creator".
Currently we are using Pack CLI to create application image with NewRelic in it.
pack build "$CI_REGISTRY_IMAGE" --builder "paketobuildpacks/builder:latest" --volume "$(pwd)/binding:/platform/bindings/new-relic" -b paketo-buildpacks/java -b paketo-buildpacks/new-relic --env BP_JVM_VERSION=17
We would like to do same using "creator", the document says "" --> Path to buildpacks directory (see Buildpacks Directory Layout)
However its not very clear how to add buildpack with "creator"
Proposed solution
Add a example or more documentations with clear usage
The text was updated successfully, but these errors were encountered: