search

luxas / kubernetes-on-arm

Kubernetes ported to ARM boards like Raspberry Pi.
MIT License
597 stars 86 forks source link

0.7 k8s fails after reboot #112

Closed mjudeikis closed 7 years ago

mjudeikis commented 8 years ago

As discussed in in other issue:

[root@k8s-master ~]# kube-config info
Architecture: armv7l
Kernel: Linux 4.4.15
CPU: 4 cores x 1200 MHz

Used RAM Memory: 135 MiB
RAM Memory: 922 MiB

Used disk space: 2.7GB (2773068 KB)
Free disk space: 53GB (55253568 KB)

SD Card/deb package was built: 18-07-2016 20:11

kubernetes-on-arm: 
Latest commit: 1d0bbe1
Version: 0.7.0

systemd version: v230
docker version: v1.10.0
kubernetes server version: v1.2.0

CPU Time (minutes):
kubelet: 0:15
kubelet has been up for: About a minute
apiserver: 0:15
controller-manager: 0:03
scheduler: 0:00
proxy: 0:00
[root@k8s-master ~]# kube-config info
Architecture: armv7l
Kernel: Linux 4.4.15
CPU: 4 cores x 1200 MHz

Used RAM Memory: 135 MiB
RAM Memory: 922 MiB

Used disk space: 2.7GB (2773068 KB)
Free disk space: 53GB (55253568 KB)

SD Card/deb package was built: 18-07-2016 20:11

kubernetes-on-arm: 
Latest commit: 1d0bbe1
Version: 0.7.0

systemd version: v230
docker version: v1.10.0
kubernetes server version: v1.2.0

CPU Time (minutes):
kubelet: 0:15
kubelet has been up for: About a minute
apiserver: 0:15
controller-manager: 0:03
scheduler: 0:00
proxy: 0:00

Startup of k8s-master: https://gist.github.com/Mangirdaz/4857bf6502f935795b46ba2ff4ba9a17

reboot initiated: https://gist.github.com/Mangirdaz/092b8d80c9244effaadfa4036b0b1f1f

failure:

Jul 18 23:05:59 k8s-master sh[710]: See 'docker run --help'.
Jul 18 23:05:59 k8s-master systemd[1]: k8s-master.service: Main process exited, code=exited, status=125/n/a
Jul 18 23:06:01 k8s-master docker[721]: Failed to stop container (k8s-master): An error occurred trying to connect: Post http:///var/run/docker.sock/v1.22/containers/k8s-master/stop?t=10: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Control process exited, code=exited status=1
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Unit entered failed state.
Jul 18 23:06:01 k8s-master systemd[1]: k8s-master.service: Failed with result 'exit-code'.
Jul 18 23:06:06 k8s-master systemd[1]: k8s-master.service: Service hold-off time over, scheduling restart.
Jul 18 23:06:06 k8s-master systemd[1]: Stopped The Master Components for Kubernetes.
Jul 18 23:06:06 k8s-master systemd[1]: Starting The Master Components for Kubernetes...
Jul 18 23:06:08 k8s-master docker[738]: Failed to kill container (k8s-master): An error occurred trying to connect: Post http:///var/run/docker.sock/v1.22/containers/k8s-master/kill?signal=KILL: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:10 k8s-master docker[747]: Failed to remove container (k8s-master): An error occurred trying to connect: read unix /var/run/docker.sock: connection reset by peer
Jul 18 23:06:11 k8s-master systemd[1]: Started The Master Components for Kubernetes.

docker: docker.service: Failed with result 'resources'.

will give it proper debug cycle later, but suggestions and hits are more than welcome :)

luxas commented 7 years ago

v0.8.0 is released, and it does not support reboots.

Closing...

Did you ever find a solution?