Tracker for CRI-O issues #3296
Labels
co/runtime/crio
CRIO related issues
kind/documentation
Categorizes issue or PR as related to documentation.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Currently there are a lot of issues, when trying to use an alternative runtime...
https://kubernetes.io/docs/setup/minikube/#alternative-container-runtimes
Added this issue as a "tracker", to the individual pull requests that I opened earlier.
I believe all of them are needed, to again be able to use something other than Docker ?
minikube start --container-runtime=cri-o --network-plugin=cni
Especially once the default Kubernetes version is updated from 1.10 to 1.12 and beyond.
Fixes
#3154 Add config parameter for the cri socket path#3190 Improve the default crio-bin configuration#3194 Write /etc/crictl.yaml when starting#3211 Stop docker daemon, when running cri-o#3303 none driver: Only require docker for the docker runtimeFeatures
#2757 CRI: try to use "sudo podman load" instead of "docker load"#3225 CRI: Add Buildah to ISO, for building OCI imagesThe text was updated successfully, but these errors were encountered: