image-builder
image-builder copied to clipboard
kubernetes-sigs
Remove dependency on ovftool
ovftool is behind a registration wall - Govc, https://github.com/thebsdbox/gova and qemu-img should be able to replace everything in ovftool
/kind feature
I don't know if something changed with newer versions of Fusion and vSphere or what, but I spent hours trying to figure out why the tar method of creating the OVA no longer worked but OVFtool did. I could take "our" OVA, which no longer imports, untar it and rebuild it with OVFtool and it would work fine. No change to the OVF or the VMDK. I dug into tar format standards (POSIX vs GNU, etc) and all that stuff, still no luck.
So the thinking here was that anyone that is importing to vSphere (and honestly, Fusion/Workstation) is already downloading things that are behind a EULA, so this is more of the same. I would love to eventually be able to remove the dependency as well, and hopefully we can. Thanks for filing this to track that.
I was planning on solving this in the image-builder CLI and then using that as a gentle introduction to the CLI without significant impact or changes to existing processes.
Just a comment on this, the dockerfile will no longer build as the ovftool isn't present. I guess we can change the dockerfile to include this, but at the moment this does cause a problem for people who want to run image-builder without setting up all the prereqs on the agent. Could we not leave the "broken" method in place for people that want to use it even though they know there are problems importing it without govc?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
FWIW, there is no longer any dependency on ovftool, and the Dockerfile doesn't try to install it. It's an option to use if present, enabled with env vars. I think it's still worth keeping this issue around, though.
/lifecycle frozen