You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems in the provider knative, if we mention the function handler as docker file, server less use the host docker deamon and build the image and push to docker hub (given the username and password in env), But my feature request is to build the image using the Kaniko (https://github.com/GoogleContainerTools/kaniko) it is googles docker build system in kubernetes. Ans also if possible support for private container registries.
Description
What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
Here using the kaniko build system means, the developer need not to have install the docker in his system as well as for larger images the CPU power at developer system is not sufficient, if we implement this feature our image builds will be in kubernetes cluster rather than developing system.
Optional: If there is additional config how would it look
Similar or dependent issues:
No issues i found.
The text was updated successfully, but these errors were encountered:
Feature Proposal
It seems in the provider knative, if we mention the function handler as docker file, server less use the host docker deamon and build the image and push to docker hub (given the username and password in env), But my feature request is to build the image using the Kaniko (https://github.com/GoogleContainerTools/kaniko) it is googles docker build system in kubernetes. Ans also if possible support for private container registries.
Description
Here using the kaniko build system means, the developer need not to have install the docker in his system as well as for larger images the CPU power at developer system is not sufficient, if we implement this feature our image builds will be in kubernetes cluster rather than developing system.
Similar or dependent issues:
No issues i found.
The text was updated successfully, but these errors were encountered: