Suggestion: --snapshotMode=skip #1615
Labels
area/cli
bugs related to kaniko CLI
area/layers
feat/snapshotMode
kind/feature-request
priority/p3
agreed that this would be good to have, but no one is available at the moment.
I expect that my use-case is well out of scope for Kaniko, but it actually works great for it and I wanted to propose a small improvement which would be of help with it.
Basically what I've done is prepared a virtualization appliance (ovf) which on startup pulls and unpacks a container image onto its own filesystem, and then reboots into it as a VM with no containerization layer. This has the benefit of being simple for users who expect/need a VM, while also allowing lots of flexibility in how to prepare and use this image.
The core of the implementation is shipping the kaniko binary, plus a trivial Dockerfile which starts
FROM
the image I want, and then afterward has someRUN
lines to install and set up the kernel, bootloader, etc. So then it's just an init script which basically does:But despite
--no-push
, this still takes the time afterward to crawl the whole filesystem looking for changes:Assuming there's a valid use-case for Kaniko to create the image when passed
--no-push
, could there either be a no-op snapshot mode, or perhaps a similar--no-snapshot
flag? Alternatively, I'd be happy to hear if there are suggestions for other, possibly lower-level tools which would handle the "Pull multi-layer image from registry, unpack it to/
" piece of the puzzle.The text was updated successfully, but these errors were encountered: