The name of the make variable was changed
Unfortunately there is no naming standard whatsoever,
for these magic make variables for the git commit...
Upgrade crio.conf to version v1.18.1
The repository was moved to a separate organization
strings.ReplaceAll only work in go1.12, not go1.10
Need to create conmon/config.h without tags and git
The configuration _needs_ to be updated (yet again)
Also, this fixes the version output from `kubectl describe node`.
Now it shows:
```
[...]
System Info:
Machine ID: 41af387f4d4e4a3eabcdd2454a7e17f9
System UUID: B5BA9F83-3476-4B4A-943A-81E7A3953234
Boot ID: 7e616123-fa50-4fa9-8f47-88b2a09fbb81
Kernel Version: 4.9.13
OS Image: Buildroot 2017.02
Operating System: linux
Architecture: amd64
Container Runtime Version: cri-o://1.0.3
Kubelet Version: v1.8.0
Kube-Proxy Version: v1.8.0
[...]
```
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
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>