On Thu, Apr 25, Sascha Grunert wrote:
I'm not sure If this kind of adaptions to the
package are the right way to solve
the configuration problems, so I would propose an additional change for the next
upcoming major version of CRI-O: As far as I understood was the problem that
CRI-O does not start if there is a CNI plugin directory configured which does
Let's say it this way: configuring standard directories, which do not exist,
is always a bad idea.
This could even become a security problem.
Other projects like Cilium would run as DeamonSets on
where CRI-O surely has to be started before. To fix this, I changed the upstream
behavior for the CNI plugin directory validation that not existing directories
will be created automatically by CRI-O . This makes the following lines in
the spec obsolete for the next major (v1.15.0) release:
# This is the additional directory where cri-o is going to look up for CNI
# plugins installed by DaemonSets running on Kubernetes (i.e. Cilium).
mkdir -p /opt/cni/bin
I would prefer to fix it "correct": Add /opt/cni/bin as directory to the
filelist of the "right" RPM, whichever this is. Or use systemd-tmpfiles
to create it.
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg)
To unsubscribe, e-mail: opensuse-kubic+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kubic+owner(a)opensuse.org