#kaniko — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kaniko, aggregated by home.social.
-
Replacing Kaniko with Buildah in a Tekton Pipeline worked like a charm...
-
Replacing Kaniko with Buildah in a Tekton Pipeline worked like a charm...
-
Kaniko has been archived by Google last year. Chainguard forked the repository, but does not publish images (for free).
https://github.com/GoogleContainerTools/kaniko
https://github.com/chainguard-forks/kanikoWhat is everyone using for their image builds inside containers (as a drop-in replacement, I know about apko and other tools)?
#DevOps #Kuberneters #Docker #Containers #Kaniko #AdminLife #Pipelines #CICD #HomeLab
-
Kaniko has been archived by Google last year. Chainguard forked the repository, but does not publish images (for free).
https://github.com/GoogleContainerTools/kaniko
https://github.com/chainguard-forks/kanikoWhat is everyone using for their image builds inside containers (as a drop-in replacement, I know about apko and other tools)?
#DevOps #Kuberneters #Docker #Containers #Kaniko #AdminLife #Pipelines #CICD #HomeLab
-
#kaniko fork call for new maintainers :)
If you are interested checkout https://github.com/osscontainertools/kaniko/discussions/304
#golang #cicd #foss #opensource #maintenance #fork #keepalive
-
@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 -
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.
-
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.
-
Interesting, #kaniko has been archived.
Need to change all my gitlab-ci pipelines to something else now 😓 #gitlab #hubernetes -
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_A4KTMChainguard already announced its fork of Kaniko:
https://github.com/chainguard-dev/kanikoI hope we'll see longstanding issues resolved as well as hurdles for other tools removed.
-
Из 2024 в 2025: вспоминаем лучшие практики CI/CD
Развитие методологий CI и CD не стоит на месте. Тем не менее, проверенные практики, вероятно, останутся актуальными и в 2025 году. В этой статье покажем некоторые из таких в действии. Вспомнить лучшие практики CI/CD
https://habr.com/ru/companies/nixys/articles/841174/
#gitlabci #argocd #flux #vault #cicd #kaniko #kubernetes #инфраструктура #доставка_кода
-
Looks like #kaniko is unmaintained. Bad to see as it was my first stop https://github.com/GoogleContainerTools/kaniko/issues/3348
probably taking a look at #buildah or #Nix to do the job in the future -
Looks like #kaniko is unmaintained. Bad to see as it was my first stop https://github.com/GoogleContainerTools/kaniko/issues/3348
probably taking a look at #buildah or #Nix to do the job in the future -
Awesome 🎉 #rust #rocket #digitalocean #kubernetes 👇star my code
https://github.com/giuliohome/rust-rocket-playgroundBtw podman is yet another fake #opensource #foss repository
I stop suggesting @Podman_io
I wasted my time with those stupid idiots.https://github.com/containers/podman/issues/24013
I admit that @docker is the way to go to #build a #Dockerfile
Or #containerd ctr + #kaniko !
+ #chatgpt for support 💪 instead of github useless maintainers -
Awesome 🎉 #rust #rocket #digitalocean #kubernetes 👇star my code
https://github.com/giuliohome/rust-rocket-playgroundBtw podman is yet another fake #opensource #foss repository
I stop suggesting @Podman_io
I wasted my time with those stupid idiots.https://github.com/containers/podman/issues/24013
I admit that @docker is the way to go to #build a #Dockerfile
Or #containerd ctr + #kaniko !
+ #chatgpt for support 💪 instead of github useless maintainers -
@boo_ @federico3 yeah, I recently had problems running a base image #Container in #PodMan on an older VM because it had a single #Docker layer that was not #OCI compliant even though it was built on #Kaniko 😡
Newer versions of podman have no problem with the non compliant image, but I'm constrained to use the older one. Unfortunately, while #Nix is great for consistent Dev shells, and building container images, it's not great at installing container runners like podman and Docker 🤷♂️
-
@boo_ @federico3 yeah, I recently had problems running a base image #Container in #PodMan on an older VM because it had a single #Docker layer that was not #OCI compliant even though it was built on #Kaniko 😡
Newer versions of podman have no problem with the non compliant image, but I'm constrained to use the older one. Unfortunately, while #Nix is great for consistent Dev shells, and building container images, it's not great at installing container runners like podman and Docker 🤷♂️
-
@deliverance If #Kaniko is not your speed, You can still do better than #DinD by using #PinD or even #PinP
How to use Podman inside of a container
https://www.redhat.com/sysadmin/podman-inside-containerThis way you don't need a daemon, and you can run rootless.
-
@deliverance If #Kaniko is not your speed, You can still do better than #DinD by using #PinD or even #PinP
How to use Podman inside of a container
https://www.redhat.com/sysadmin/podman-inside-containerThis way you don't need a daemon, and you can run rootless.
-
@deliverance You might want to consider #kaniko.
Building Docker images without Docker using Kaniko + Gitlab CI and AWS | by Raphael Moraes | Webera
https://webera.blog/building-docker-images-without-docker-using-kaniko-gitlab-ci-and-aws-c85ee802a4b -
@deliverance You might want to consider #kaniko.
Building Docker images without Docker using Kaniko + Gitlab CI and AWS | by Raphael Moraes | Webera
https://webera.blog/building-docker-images-without-docker-using-kaniko-gitlab-ci-and-aws-c85ee802a4b -
Ooof, late night debugging stuff and it looks like #kaniko totally ignores heredocs. And here I thought it was some kind of black magic that was _removing_ my files and it was happily skipping those layers entirely. https://github.com/GoogleContainerTools/kaniko/issues/1713
-
Ooof, late night debugging stuff and it looks like #kaniko totally ignores heredocs. And here I thought it was some kind of black magic that was _removing_ my files and it was happily skipping those layers entirely. https://github.com/GoogleContainerTools/kaniko/issues/1713
-
#Kaniko seems to be injecting a non OCI compliant layer into image builds, which breaks my ability to use those images with #podman
Some of the big picture links I've looked at while trying to understand this problem:
* Learning #Docker in Docker with Docker - Toying with DinD For Fun and Profit https://iximiuz.com/en/posts/containers-learning-docker-with-docker/
* Learning Containers From The Bottom Up https://iximiuz.com/en/posts/container-learning-path/
* kaniko - Build Images In Kubernetes https://github.com/GoogleContainerTools/kaniko#readme
-
#Kaniko seems to be injecting a non OCI compliant layer into image builds, which breaks my ability to use those images with #podman
Some of the big picture links I've looked at while trying to understand this problem:
* Learning #Docker in Docker with Docker - Toying with DinD For Fun and Profit https://iximiuz.com/en/posts/containers-learning-docker-with-docker/
* Learning Containers From The Bottom Up https://iximiuz.com/en/posts/container-learning-path/
* kaniko - Build Images In Kubernetes https://github.com/GoogleContainerTools/kaniko#readme
-
so sabia que #portainer puede aplicar #gitops para #container dentro de un #docker compose interesante y mas aun con la habilitación del #webhook ya despues montare un post de como hacer esta integracion con pipelines en #gitlab y #kaniko + #jfrog
-
Short guide about how to build Docker images with kaniko on Kubernetes-based GitLab Runners
👇🏻
https://www.pachamamita.de/posts/kubernetes/kaniko-gitlab-runner/ -
@dragnucs Difficult and embarassing topic.
I wrote prototypes for Terraform Providers for #podman, #buildah and #kaniko IIRC.
ALL of them are horrible at caching layers - let alone remote exec.
The only descend approach which supports caching seems to be #buildx + #buildkit. And yes, I have a prototype implementation for that as well.
We are still not testing this though, since hosting a Buildkit Remote Builder on GKE is a nightmare.
Let alone error handling in both buildx and buildkit is BAD.
