CRI-O systemd unit not picking up /etc/sysconfig/crio.minikube and thus not setting --insecure-registry

[tliron]

Steps to reproduce the issue:

Started thus:

minikube start \
	--vm-driver=kvm2 \
	--container-runtime=cri-o \
	--cni=bridge \
	--addons=registry \
	--cpus=4 \
	--service-cluster-ip-range=10.96.0.0/12

Now, do minikube ssh and:

sudo systemctl status crio

You will see that the command used is /usr/bin/crio --log-level=debug. However, this is incomplete. Looking at /etc/systemd/system/multi-user.target.wants/crio.service you will see that it refers to /etc/sysconfig/crio.minikube, which importantly has extra arguments for --insecure-registry. However, it seems that /etc/sysconfig/crio.minikube was not used.

This breaks the registry add-on out of the box.

As a workaround, do a quick:

sudo systemctl restart crio
sudo systemctl status crio

And you will see that --insecure-registry has now been set properly.

My guess is that somehow the "crio.minikube" file was create too late during the setup process.