Hans Feldt a2d4dbeee4 crio: use system default for storage driver by default (#6637) ... After host reboot kubelet and crio goes into a loop and no container is started. storage_driver in crio.conf overrides system defaults in etc/containers/storage.conf /etc/containers/storage.conf is installed by package containers-common dependency installed from cri-o (centos7) and contains "overlay". Hosts already configured with overlay2 should be reconfigured and the /var/lib/containers content removed.		2020-09-10 05:29:45 -07:00
..
defaults	crio: use system default for storage driver by default (#6637)	2020-09-10 05:29:45 -07:00
files	Split deploy steps in separate playbooks: part1 (#3451)	2018-10-09 19:14:33 -07:00
handlers	Add CRI-O CI (#5460)	2020-04-22 06:09:52 -07:00
molecule/default	Upgrade molecule to v3 (#6468)	2020-08-04 05:24:19 -07:00
tasks	Fix ansible-lint E305 (#6459)	2020-07-28 01:39:08 -07:00
templates	crio: use system default for storage driver by default (#6637)	2020-09-10 05:29:45 -07:00
vars	fix CRI-O repos for centos distributions (#6224)	2020-06-04 01:08:44 -07:00