3 ms·
The benefit of Kaniko (relative to Docker-in-Docker) is that you don't need to run in privileged mode. We test our containers in our Dev environment after depl
by goodoldneon 4y ago
The benefit of Kaniko (relative to Docker-in-Docker) is that you don't need to run in privileged mode.
We test our containers in our Dev environment after deploying
- alexellisuk 4y agoThat is a benefit over DIND and socket sharing, however it doesn't allow for running containers or K8s itself within a job. Any tooling that depends on running "docker" (the CLI) will also break or need adapting. This also comes to mind: "root in the container is root on the host" - https://suraj.io/post/root-in-container-root-on-host/ https://suraj.io/post/root-in-container-root-on-host/
- mattbillenstein 4y agoThis reminds me of the erlang map-reduce "did you just tell me to fuck myself" meme