-
Notifications
You must be signed in to change notification settings - Fork 138
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
Support configuration of the lifecycle
image
#2184
Comments
This seems like a bug to me. I will mark it as such. It's perhaps worth mentioning that the builder lifecycle image is not intended as "hard-coded" (meaning an unchangable string built into the binary), but rather it is defaulted. This should be an optional user-modifiable setting. |
I agree @lkingland however does |
I would like to work on this issue! |
/assign |
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
When you run a build with the
func
CLI using your own builder it will attempt to pull the lifecycle binaries fromquay.io
. This may be because the builder is not trustedHowever it doesn't seem that the
func
CLI respects the list of trusted builders that a user configures with the Pack CLI, and also does not allow configuration of this property itself. This means that at runtimefunc
will attempt to pull the lifecycle fromquay.io
. The image thatfunc
pulls is hardcoded here:func/pkg/builders/buildpacks/builder.go
Line 117 in 51f7a70
This should allow configuration, or allow configuration of trusted builders so the built in lifecycle binaries can be used.
The text was updated successfully, but these errors were encountered: