When the CRI-O container storage backend is used, loading images using
`podman load` creates temporary files in /var/tmp. As /var/tmp is
mounted as tmpfs, these temporary files rapidly consume the available memory
and cause processes on the minikube VM to be OOM-killed.
Instead, bind mount /var/tmp like we do with /var/log, which will write
temporary files to disk instead of memory.
https://github.com/kubernetes-incubator/cri-o
Updated the runc version to its latest master commit.
Got crio into the automounter to get off the tmpfs
This feature bubbles up to the minikube command by reusing the
`--container-runtime=` flag, by enabling the value of "`crio`"
(`minikube start --container-runtime=crio`), while the flags/config
passed to localkube are more like k8s (`--container-runtime=remote
--remote-runtime-endpoint=/var/run/crio.sock`)
This is mostly ready for review. It is still lacking having
--insecure-registry plumbed through, but for now the policy.json is
open.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
Journalctl has not been logging properly in the minikube-iso because of
the absence of /var/log on startup. This is an issue now that we are
using systemd for localkube. This commit links and persists the directory
/var/log like we do for other folders.
Francis Laniel
Blaine Gardner
Anders F Björklund
Medya Gh
Anshul Sirur
Thomas Strömberg
Aaron Prindle
Vincent Batts
Praveen Kumar
dlorenc
Dale Hamel
Bryan Larsen
dlorenc
Matt Rickard
Tom von Schwerdtner
Sergiusz Urbaniak