I had a dataset with mountpoint=/var/lib/crio
cri-o fails to start with
msg="validating root config: failed to get store to set defaults: no zfs dataset found for rootdir '/var/lib/crio': prerequisites for driver not satisfied (wrong filesystem?)"
it does create some files like storage.lock, userns.lock and zfs folder.
changing graphroot to /var/lib/crio/containers makes it start properly
What did you expect to happen?
use /var/lib/crio as as a storage folder instead of having to add additional subfolder
How can we reproduce it (as minimally and precisely as possible)?
apt-get install cri-o
zfs create pool/crio
zfs set mountpoint=/var/lib/crio pool/crio
What happened?
I had a dataset with mountpoint=/var/lib/crio cri-o fails to start with
it does create some files like storage.lock, userns.lock and zfs folder.
changing graphroot to /var/lib/crio/containers makes it start properly
What did you expect to happen?
use /var/lib/crio as as a storage folder instead of having to add additional subfolder
How can we reproduce it (as minimally and precisely as possible)?
apt-get install cri-o
zfs create pool/crio zfs set mountpoint=/var/lib/crio pool/crio
/etc/containers/storage.conf:
systemctl start crio
Anything else we need to know?
happened on crio 1.31, OS Debian 12, repo https://pkgs.k8s.io/addons:/cri-o:/stable:/v1.31/deb/, zfs 2.1
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)