Implementing docker build command with Kaniko

[ismailbaskin]

Hi,

I've observed that our current feature set lacks support for the docker build command. To enrich our capabilities, I propose the use of Kaniko, a tool designed to build Docker images in environments such as Kubernetes, without a Docker daemon.

My suggestion is to trigger a Kaniko Job on each docker build command issued, allowing the Docker image to be built and pushed directly to the specified registry within the Kubernetes cluster.

I believe this addition would significantly streamline Docker image building and deployment processes, especially beneficial in CI/CD contexts.

I'm eager to discuss this further and potentially contribute to its implementation.

Thanks.

[joyrex2001]

From an implementation perspective, I would like to offload this to something pluggable. For example, if a build call is made, it would offload it to another service which would build and publish the container. This would move most of the complexity to another layer (which can used kaniko, buildah, ... to build), and would have the registry config complexity managed there as well. Maybe directly proxying the relevant API call(s) to a pre-configured endpoint in kubedock would be sufficient in that case.

[djmcgreal-cc]

Came here to suggest the same thing.

[gecube]

kaniko looks dead. Any suggestsions?

[joyrex2001]

An alternative could be buildah, but an implementation in kubedock should be agnostic towards tooling. It should provide the proper hooks to help integrate any kind of container build solution.

[djmcgreal-cc]

Encapsulate all that in something like https://shipwright.io?