This is used by both crio and podman, one bin for each

But we try to use the same version, unless we have to...

Currently it is showing the "dirty" status of buildroot,
due the build script picking the wrong git repository...

runc version 1.0.0-rc10
commit: dc9208a3303feef5b3839f4323d9beb36df0a9dd-dirty

For some reason this got lost with previous commit

When the CRI-O container storage backend is used, loading images using
`podman load` creates temporary files in /var/tmp. As /var/tmp is
mounted as tmpfs, these temporary files rapidly consume the available memory
and cause processes on the minikube VM to be OOM-killed.

Instead, bind mount /var/tmp like we do with /var/log, which will write
temporary files to disk instead of memory.

Signed-off-by: NYang Keao <keao.yang@yahoo.com>

        containerd v1.2.13

We can use preloaded tarballs for VMs as well, but this requires both
lz4 and tar to be installed to that the tarball can be extracted
correctly within the VM.

No changes to the actual driver, though...

And make sure to install cnitool, not noop (!)

"DHCP: No gateway received from DHCP server"

Fails systemd-networkd-wait-online.service

Not to be confused with sysdig package (0.23.1)

Generated with `containerd config default`

The minikube iso is using systemd, so change the container runtime
to use the same cgroup manager instead of the default (cgroupfs).

Avoids kubeadm init message:
    [WARNING IsDockerSystemdCheck]:
        detected "cgroupfs" as the Docker cgroup driver.
        The recommended driver is "systemd".

Also change the configuration for the containerd and cri-o runtimes.

Apparently my amend failed, had exact same hash as podman-1.6.4

runc v1.0.0-rc10

    containerd v1.2.12

* Upgrade crio to 1.17.0

* Upgrade crio.conf to version v1.17.0