kubernetes: "classic" networking fails to start in k8s 1.4

If not using kubenet, but using “classic” networking, kubelet fails to start on k8s 1.4

kubelet is waiting for docker to start:

Sep 29 21:02:05 ip-172-20-99-157 kubelet[4077]: E0929 21:02:05.727512    4077 docker_manager.go:238] Failed to execute Info() call to the Docker client: An error occurred trying to connect: Get http://%2Fvar%2Frun%2Fdocker.sock/info: read unix @->/var/run/docker.sock: read: connection reset by peer

Docker is waiting for kubelet to create cbr0:

Sep 29 21:01:53 ip-172-20-99-157 docker[4030]: time="2016-09-29T21:01:53.379504146Z" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default \"bridge\" network: bridge device with non default name cbr0 must be created manually"

cc @thockin either I’m doing something wrong or we need to document that non-kubenet is no longer supported.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 18 (15 by maintainers)

Commits related to this issue

Most upvoted comments

has anyone encountered this issue in 1.5 or 1.6?