osscontainertools

osscontainertools

We are the community continuation of kaniko. When Google stopped developing it in 2024, we took it over, so the many CI pipelines that build their images with kaniko have a maintained future.

osscontainertoolsGoogle202520262024-10Development at Googlestalls. We fork kaniko asmzihlmann/kaniko.2025-05Our first release, the dayafter Google's last.2025-06Google archives the originalrepository.2025-09mzihlmann/kaniko moves tothe osscontainertoolsorganisation.

Who we are

0hlov3 0hlov3 babs babs BobDu BobDu mzihlmann mzihlmann nejch nejch

We are five maintainers who rely on kaniko in our own CI. When it was archived, we came together to keep it alive and moving forward.

Get involved →

Principles

🔒 Unprivileged

No daemon, no privileged container, no namespaces or mounts. kaniko runs wherever a plain container runs, and that will not change.

🪞 Compatible

A Dockerfile should build the same with kaniko as with BuildKit. Where the two differ, we close the gap.

🏁 No surprises

Behaviour changes arrive behind a feature flag and become the default only on a published schedule.

🌐 Open

Development happens in public, decisions are made on technical merit, and everything we publish is Apache-2.0.

Projects

kaniko

Builds container images from a Dockerfile inside a container or a Kubernetes cluster, without a Docker daemon and without privileges.

docker-credential-acr

A credential helper for Azure Container Registry, made for CI. It ships inside every kaniko image.

Sponsors

L3montree Siemens

Sped0n bootc

Buy us a coffee →

Blog

No.TitleDate
OSSCT-2026-001 kaniko and BuildKit: 8 years later 2026-09-27