ISO: install more packages by binary vs (build from source)

[medyagh]

Here are the components built from source, with their definitions:

Build from Source

• cni
  deploy/iso/minikube-iso/package/cni/cni.mk:8

• podman
  deploy/iso/minikube-iso/package/podman/podman.mk:3

• runc-master
  deploy/iso/minikube-iso/package/runc-master/runc-master.mk:9

• crun-latest
  deploy/iso/minikube-iso/package/crun-latest/crun-latest.mk:10

• cri-dockerd
  deploy/iso/minikube-iso/arch/x86_64/package/cri-dockerd/cri-dockerd.mk:10

• docker-buildx
  deploy/iso/minikube-iso/arch/x86_64/package/docker-buildx/docker-buildx.mk:9

• hyperv-daemons
  deploy/iso/minikube-iso/arch/x86_64/package/hyperv-daemons/hyperv-daemons.mk:8

---

📦 Install from Binary:

crio-bin
crictl-bin
containerd-bin
docker-bin
buildkit-bin
nerdctl-bin
cni-plugins-latest
vbox-mount-service

[medyagh]

I dont think installing these things from source take that much time but I think the super stable ones should be moved to binary
wdyt @afbjorklund which one we should move to installing from binary

[afbjorklund]

I think that you should build more things from source, and clean up the packages instead of trusting the upstream.

They can also reuse the existing infrastructure, and don't have to use broken upstream packaging or reinvent the wheel.

There is some cleanup to be done with names, and should avoid things like "latest" or "master" when they are older?

---

Using host-go-bin (and host-rust-bin) is a good improvement, as those tools take a long time to bootstrap every time.

Eventually all the compilers can go in the "SDK" tarball, then gcc does not need to be built either. But that's for tools.

• Speed up the build times in CI for the ISO buildroot #22147

[afbjorklund]

The main reason that these are slow, is that they are not using the cache infrastructure for build and download.

So instead of just using the build cache for a quick rebuild, they are building and pulling all modules every time.

But you can pull the container runtimes from binary like we pull the three kubernetes programs already.

Especially if they are not going to be included in the ISO image (at all), but installed by minikube at runtime?

[afbjorklund]

I think that "hyperv-daemons" and "vbox-mount-service" can be left as they are, they are not part of the runtimes.

[afbjorklund]

• Refactor the names and versions of packages in ISO buildroot #22137

[afbjorklund]

The list is missing "conmon", which is included in buildroot and not updated in minikube (probably a mistake).

BR2_PACKAGE_CONMON

This package is similar to containerd (for podman), just like crun is similar to runc (for podman) and is important.

https://github.com/containers/conmon