Build Container Images In Kubernetes

★ 15,745⑂ 1,523👁 3⑃ 1,890● 1,596▤ 61
GoApache-2.0Created 2018-01-29
More from this author
Download: v1.24.0v1.24.0 ↓1.24.02025-05-23
+1
Daily
15,745
stars
1,523
forks
3
watchers
1,890
prs
1,596
issues
61
releases

README

🧊 This project is archived and no longer developed or maintained. 🧊

The code remains available for historic purposes.

The README as of the archival date remains unchanged below for historic purposes.

-----

 kaniko - Build Images In Kubernetes

 🚨NOTE: kaniko is not an officially supported Google product🚨






!kaniko logo

kaniko is a tool to build container images from a Dockerfile, inside a container
or Kubernetes cluster.

kaniko doesn't depend on a Docker daemon and executes each command within a
Dockerfile completely in userspace. This enables building container images in
environments that can't easily or securely run a Docker daemon, such as a
standard Kubernetes cluster.

kaniko is meant to be run as an image: gcr.io/kaniko-project/executor. We do
not recommend running the kaniko executor binary in another image, as it
might not work as you expect - see Known Issues.

We'd love to hear from you! Join us on
kaniko Kubernetes Slack

:mega: Please fill out our
quick 5-question survey so that we can
learn how satisfied you are with kaniko, and what improvements we should make.
Thank you! :dancers:

_If you are interested in contributing to kaniko, see
DEVELOPMENT.md and CONTRIBUTING.md._




Table of Contents _generated with
DocToc_

- kaniko - Build Images In Kubernetes
  - 🚨NOTE: kaniko is not an officially supported Google product🚨
  - Community
  - How does kaniko work?
  - Known Issues
  - Demo
  - Tutorial
  - Using kaniko
    - kaniko Build Contexts
    - Using Azure Blob Storage
    - Using Private Git Repository
    - Using Standard Input
    - Running kaniko
      - Running kaniko in a Kubernetes cluster
        - Kubernetes secret
      - Running kaniko in gVisor
      - Running kaniko in Google Cloud Build
      - Running kaniko in Docker
    - Caching
      - Caching Layers
      - Caching Base Images
    - Pushing to Different Registries
      - Pushing to Docker Hub
      - Pushing to Google GCR
      - Pushing to GCR using Workload Identity
      - Pushing to Amazon ECR
      - Pushing to Azure Container Registry
      - Pushing to JFrog Container Registry or to JFrog Artifactory
    - Additional Flags
      - Flag --build-arg
      - Flag --cache
      - Flag --cache-dir
      - Flag --cache-repo
      - Flag --cache-copy-layers
      - Flag --cache-run-layers
      - Flag --cache-ttl duration
      - Flag --cleanup
      - Flag --compressed-caching
      - Flag --context-sub-path
      - Flag --custom-platform
      - Flag --digest-file
      - Flag --dockerfile
      - Flag --force
      - Flag --git
      - Flag --image-name-with-digest-file
      - Flag --image-name-tag-with-digest-file
      - Flag --insecure
      - Flag --insecure-pull
      - Flag --insecure-registry
      - Flag --label
      - Flag --log-format
      - Flag --log-timestamp
      - Flag --no-push
      - Flag --no-push-cache
      - Flag --oci-layout-path
      - Flag --push-retry
      - Flag --registry-certificate
      - Flag --registry-client

Top issues

Discussions

Latest release

v1.24.0 v1.24.0 2025-05-23
v1.24.0 Release 2025-05-21
The executor images in this release are:

gcr.io/kaniko-project/executor:v1.24.0
gcr.io/kaniko-project/executor:latest


The debug images are available at:

gcr.io/kaniko-project/executor:debug
gcr.io/kaniko-project/executor:v1.24.0-debug


The slim executor images which don't contain any authentication binaries are available at:

gcr.io/kaniko-project/executor:slim
gcr.io/kaniko-project/executor:v1.24.0-slim



Dependency Updates:
 chore(deps): bump google.golang.org/grpc from 1.64.0 to 1.64.1 by @dependabot in https://github.com/GoogleContainer

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON