Env: Vbox on a Windows 10 desktop machine Two ubuntu virtual machines, one VM is the host and the other is k8s (1.7).
I see that the two nodes are “ready” when receiving the nodes. But even deploying a very simple Nginx pod, I got an error message from the pod describing <strong> "norm | SandboxChanged |. Under the sandbox changed, it will be killed and recreated" and "<strong> warning | FailedSync | Sync error pod". But if I started the docker container directly at the worker, the container can be started and started. Anyone have a suggestion what can I check for?
k8s-master @ k8smaster-VirtualBox: ~ $ kubectl get pods
NAME READINESS STATE RESTORE movie-server-1517284798-lbb01 0/1 CrashLoopBackOff 6 16m
k8s-master @ k8smaster-VirtualBox: ~ $ kubectl describe pod movie-server-1517284798-lbb01
--- clip --- kubelet, master-VirtualBox spec.containers {movie server} Warning FailedError: failed to start container "movie- server ": error response from the daemon: {" message ":" cannot join the network in an idle container: 3f59947dbd404ecf2f6dd0b65dd9dad8b25bf0c418aceb8cf666ad0761402b53 "}
kubelet, master-virtualbox spec.containers {movie-server} Warning BackOffBack-off restarting a failed container
kubelet, master-virtualbox The normal SandboxChanged Pod sandbox has changed, it will be killed and recreated.
kubelet, master-virtualbox spec.containers {movie-server} The regular PulledContainer image "nancyfeng / movie-server: 0.1.0" is already present on the machine
kubelet, master-virtualbox spec.containers {movie-server} Normal Created container
kubelet, master-virtualbox Warning FailedSync Synchronization error pod
kubelet, master-VirtualBox spec.containers {movie-server} Warning FailedError: failed to start the movie-server container: error response from the daemon: {"message": "cannot connect to the network in the broken container: 72ba77b25b6a3969e8921214f0ca73ffaab4c82d8a2852e3d1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de1de - clip ---