cf5b0ae57f
container-storage-setup (Formerly docker-storage-setup) is being converted to run with container runtimes outside of docker. Specifically we want to use it with CRI-O/ocid. It does not know anything about the container runtimes it is generating options for, so it generates them based on the storage CLI of docker. I see no reason to have the storage option for ocid to be different and we can just depracate the option for now. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> |
||
---|---|---|
.. | ||
kpod-launch.1.md | ||
kpod.1.md | ||
ocid.8.md | ||
ocid.conf.5.md |