Kaniko v1.27.0 is out!

And like a camel it comes with two new mount-options. You can now use cache & secret mounts as you would in other builders:

RUN --mount=type=secret,id=netrc,target=/root/.netrc \ --mount=type=cache,target=/root/.cache/uv \ uv pip install -r requirements.txt

Find this and more QoL improvements in our latest release notes: https://github.com/osscontainertools/kaniko/releases/tag/v1.27.0

#kaniko

Release v1.27.0 · osscontainertools/kaniko

v1.27.0 Release 2026-03-05 Update Notice In this Release we activated two feature-flags: FF_KANIKO_RUN_MOUNT_SECRET FF_KANIKO_OCI_STAGES This will allow you to use the type=secret mount option in...

GitHub
🚀 Call for Maintainers — Help Shape the Future of Kaniko · osscontainertools kaniko · Discussion #304

Hi everyone 👋 As many of you know, the original Kaniko project, developed and maintained by Google, has unfortunately been archived. To keep Kaniko alive, for myself and others, I started this comm...

GitHub

@moehrenfeld Hey did you consider using Podman? I was just discovering #Kaniko when that project was declared abandoned.

#Podman is the #Docker I always wanted and I have just set up a CI pipeline building images with Podman with #GitLab's default runners without special privileges.

See here for current MR with relevant changes:
https://floss.social/@coocook/115286756593455425

Coocook.org (@[email protected])

Hey developers! I’ve been working on a new CI setup to build Docker images for every push. What would you expect from such a setup? We’ll have a container registry for runtime/development each, with tags for every branch and for #Perl version (latest vs oldest supported). Read the new README section: https://gitlab.com/coocook/coocook/-/blob/dist-docker/README.md?ref_type=heads#run-with-dockerpodman Feel free to reply here or at the MR: https://gitlab.com/coocook/coocook/-/merge_requests/262 The MR also contains more specific review questions. #Docker #Podman #Gitlab #CICD #GitLabCI #FOSS

FLOSS.social

So I've migrated a container build pipeline from (deprecated) #Kaniko to (shiny new) #BuildKit after reading documentation from #Gitlab on how to integrate image building in Gitlab CI/CD. Turns out the whole thing doesn't work without enabling privileged mode on the Gitlab runner. Judging from the discussion around the issue there is no tool except Kaniko that works without some sort of extended privileges.

https://gitlab.com/gitlab-org/gitlab-runner/-/issues/38957

💔The End of an Era: Kaniko Has Been Archived

Kaniko built without limits - now it rests. Explore its journey from innovation to archive, and what’s next for container builds.

thehapyone
Kaniko zostało porzucone i zamknięte. Ale się szykuje migracja...

https://github.com/GoogleContainerTools/kaniko/issues/3348

#devops #kaniko #docker #k8s #kubernetes
Interesting, #kaniko has been archived.
Need to change all my gitlab-ci pipelines to something else now 😓 #gitlab #hubernetes

Google's discontinuation of #Kaniko will hopefully pave the way for better container image build tools. These have been around for quite a while, but integration into common platforms only worked flawlessly 99% of the way.

I explained the reasons in my #ContainerDays talk last year:

https://speakerdeck.com/f30/unprivileged-image-builds-what-are-the-challenges-and-where-are-we-today
https://youtu.be/62p6v_A4KTM

Chainguard already announced its fork of Kaniko:
https://github.com/chainguard-dev/kaniko

I hope we'll see longstanding issues resolved as well as hurdles for other tools removed.

Unprivileged Image Builds: What are the Challenges and Where are we Today?

<em>Recording of the talk available at: https://youtu.be/62p6v_A4KTM</em> Most popular container image build tools require extensive privileges to pe…

Speaker Deck
Fork Yeah: We’re Bringing Kaniko Back

Chainguard is taking over the maintenance of the Kaniko project, recently deprecated by Google. Learn more about why we're doing it and what is next.

Still livid that #Google killed off #kaniko, and are trying to retroactively claim it wasn't theirs despite being introduced on their blogs, presented in their presentations, pushed in their k8s docs, and existing in their github org developed by their engineers.