Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Kaniko

github.com

  • Free plan
  • Linux
  • Self-hosted
7.0 Club score Visit github.com

What Kaniko is

Kaniko is a free tool that builds container images from Dockerfiles inside a container or Kubernetes cluster without depending on a Docker daemon. It runs Dockerfile commands in userspace. During a build, its executor extracts the base image filesystem, runs the instructions, snapshots filesystem changes, and pushes the resulting image to a registry. Build contexts can come from local directories or tar files, standard input, GCS, S3, Azure Blob Storage, or Git repositories. The documentation describes running Kaniko in Kubernetes, gVisor, Google Cloud Build, and Docker. Official container support includes linux/amd64 and linux/arm64, with linux/s390x and linux/ppc64le support caveated for debug images. Kaniko does not build Windows containers or create multi-architecture manifests itself. It relies on container runtime security features and does not make untrusted builds safe on its own. Build tracing is off by default and can export build details to an OpenTelemetry collector when enabled. Images from version 1.24.1 onward are signed with cosign, with keyless verification instructions provided.

Who it suits

Kaniko suits teams building container images from Dockerfiles in container-based or Kubernetes workflows. Users should account for its platform limits and ensure their runtime security practices address untrusted builds.

Good to know, and what to watch

  • Builds without a Docker daemon.
  • Accepts build contexts from several storage sources.
  • Runs in Kubernetes, gVisor, Google Cloud Build, and Docker.
  • Supports linux/amd64 and linux/arm64 containers.
  • Images from version 1.24.1 onward are cosign-signed.
  • Does not build Windows containers.
  • Does not create multi-architecture manifests itself.
  • Does not make untrusted builds safe by itself.
  • RUN --chown is unsupported.

Open-source kaniko

Free

Free plan

The verdict

Kaniko offers daemonless image builds across a range of container-oriented environments. Its Windows and manifest limitations, as well as the need to manage build security, are important considerations.

What the maker publishes

Architecture support
The documentation lists official container support for linux/amd64, linux/arm64, linux/s390x, and linux/ppc64le, with the latter two caveated for debug images. source
Build contexts
Supported build context sources include local directories or tar files, standard input, GCS, S3, Azure Blob Storage, and Git repositories. source
Build process
The executor extracts the base image filesystem, runs Dockerfile commands, snapshots filesystem changes, and pushes the resulting image to a registry. source
Daemonless builds
Kaniko does not depend on a Docker daemon and executes Dockerfile commands in userspace. source
Dockerfile support limit
Kaniko supports COPY --chown and ADD --chown but does not support RUN --chown. source
Image distribution
The project publishes release images on GitHub Container Registry and Docker Hub. source
Image signing
Kaniko images for versions 1.24.1 and later are signed with cosign, and the documentation gives instructions for keyless verification. source
Maintainers
The project website describes OSS Container Tools as five maintainers who rely on Kaniko in their own CI and continue the project as a community effort. source
Notable limits
Kaniko does not support building Windows containers or creating multi-architecture manifests itself. source
Purpose
Kaniko builds container images from Dockerfiles inside a container or Kubernetes cluster. source
Run environments
The documentation describes running Kaniko in Kubernetes, gVisor, Google Cloud Build, and Docker. source
Security
Kaniko relies on container runtime security features and says it does not by itself make untrusted builds safe to run. source
Support
The project directs community questions to GitHub issues and offers Matrix support and announcements rooms. source
Telemetry
Build tracing is off by default and can export Dockerfile instructions, build plan, cache keys, and CI attributes to an OpenTelemetry collector. source

Checked against the maker's pages on 3 Oct 2026.