Ich hab den Übeltäter gefunden:
Code
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.705802 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.705830 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.706584 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.709361 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.714056 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.714084 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.715548 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Jan 29 19:38:20 v22017115211456294 localkube: E0129 19:38:20.717059 589 file.go:76] Unable to read manifest path "/etc/kubernetes/manifests": unable to create inotify: inotify_init: too many open files
Ich hatte ganze Zeit minikube im Hintergrund laufen. Gerade in der message log entdeckt. Da war alles zugebombt damit. Kubernetes cluster gestoppt, minicube gelöscht, fertig. XD Oh man. Aber trotzdem vielen Dank für eure Hilfe.