【kruise 1.6.3部署ds报错】 #107
Description
[root@master1 templates]# k get pod -n kruise-system
NAME READY STATUS RESTARTS AGE
kruise-controller-manager-6b685f48b7-b24lp 1/1 Running 0 18m
kruise-controller-manager-6b685f48b7-j2qml 1/1 Running 0 18m
kruise-daemon-6dhjq 0/1 CrashLoopBackOff 1 (12s ago) 19s
kruise-daemon-6jcx6 0/1 CrashLoopBackOff 1 (12s ago) 19s
kruise-daemon-76zwn 0/1 Error 1 (13s ago) 19s
kruise-daemon-8njn6 0/1 CrashLoopBackOff 1 (12s ago) 19s
[root@master1 templates]# k logs -f kruise-daemon-6dhjq -n kruise-system
I0717 08:08:30.316545 1 feature_gate.go:249] feature gates: &{map[ImagePullJobGate:true]}
I0717 08:08:30.317416 1 daemon.go:101] Starting daemon on 192.168.0.62 ...
I0717 08:08:30.568324 1 request.go:622] Waited for 51.583793ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/policy/v1beta1?timeout=32s
I0717 08:08:30.618220 1 request.go:622] Waited for 101.746738ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/autoscaling/v2?timeout=32s
I0717 08:08:30.618354 1 request.go:622] Waited for 101.887138ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/networking.k8s.io/v1?timeout=32s
I0717 08:08:30.716604 1 request.go:622] Waited for 199.835665ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/autoscaling/v1?timeout=32s
I0717 08:08:30.817357 1 request.go:622] Waited for 300.507746ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/admissionregistration.k8s.io/v1?timeout=32s
I0717 08:08:30.817621 1 request.go:622] Waited for 300.705376ms due to client-side throttling, not priority and fairness, request: GET:https://169.169.0.1:443/apis/autoscaling/v2beta1?timeout=32s
I0717 08:08:31.020899 1 remote_runtime.go:72] "Connecting to runtime service" endpoint="unix:///hostvarrun/dockershim.sock"
I0717 08:08:31.021396 1 remote_runtime.go:117] "Validating the CRI v1 API runtime version"
W0717 08:08:31.116423 1 factory.go:121] Failed to new runtime service for docker (unix:///hostvarrun/docker.sock, unix:///hostvarrun/dockershim.sock): validate service connection: CRI v1 runtime API is not implemented for endpoint "unix:///hostvarrun/dockershim.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
I0717 08:08:31.116475 1 cri.go:44] "Connecting to image service" endpoint="/hostvarrun/containerd/containerd.sock"
I0717 08:08:31.116491 1 util_unix.go:103] "Using this endpoint is deprecated, please consider using full URL format" endpoint="/hostvarrun/containerd/containerd.sock" URL="unix:///hostvarrun/containerd/containerd.sock"
I0717 08:08:31.116686 1 helpers.go:227] "Finding the CRI API image version"
E0717 08:08:31.117932 1 cri.go:61] "Failed to determine CRI image API version" err="unable to determine image API version: rpc error: code = Unimplemented desc = unknown service runtime.v1.ImageService"
W0717 08:08:31.117943 1 factory.go:103] Failed to new image service for containerd (, unix:///hostvarrun/containerd/containerd.sock): unable to determine image API version: rpc error: code = Unimplemented desc = unknown service runtime.v1.ImageService
F0717 08:08:31.117953 1 main.go:69] Failed to new daemon: failed to new runtime factory: validate service connection: CRI v1 runtime API is not implemented for endpoint "unix:///hostvarrun/dockershim.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
[root@master1 templates]#
volumeMounts:
- mountPath: /hostvarrun
name: runtime-socket
readOnly: true
dnsPolicy: ClusterFirst
hostNetwork: true
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: kruise-daemon
serviceAccountName: kruise-daemon
terminationGracePeriodSeconds: 10
tolerations:
- operator: Exists
volumes:
- hostPath:
path: /var/run/
type: ""
name: runtime-socket