-
Notifications
You must be signed in to change notification settings - Fork 43
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 custom access to docker image repository #154
Conversation
Signed-off-by: wanjunlei <[email protected]>
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.
@wanjunlei thanks so much for the PR! In general this looks good to me. I added a couple comments and suggestions.
We've come across this problem before (see buildpacks/lifecycle#524) and this would take us one step closer to solving it for other components 🎉
Signed-off-by: wanjunlei <[email protected]>
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.
@wanjunlei thanks for updating! I left a couple more nits. But otherwise this seems good to go.
Signed-off-by: wanjunlei <[email protected]>
Thanks for the PR @wanjunlei! |
Signed-off-by: wanjunlei [email protected]
When creating a new imange, it can register a docker image registry with
WithRegistry
option like thisThe first parameter is the URL of the docker image registry, the second is whether this registry is an insecure registry, and the third is whether to skip TLS authentication. And it can register serval registries.
This is useful when using a private docker image registry, and this pr is for the lifecycle to support a private docker image registry.