Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker for windows kubeernets is always starting #3757

Closed
2 tasks
15313974342 opened this issue Apr 16, 2019 · 16 comments
Closed
2 tasks

docker for windows kubeernets is always starting #3757

15313974342 opened this issue Apr 16, 2019 · 16 comments

Comments

@15313974342
Copy link

我尝试了删除/kube/config 文件但是没有效果

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID:74A7C591-568B-46D7-B165-E9A9E1782CFB/20190416191014

Expected behavior

Actual behavior

Information

  • Windows Version:
  • Docker for Windows Version:

Steps to reproduce the behavior

image

@alexandrev
Copy link

+1 same happening here with 2.0.3.0 (31778) on Win 10.

--> Diagnostics ID: 04D051A9-8885-40A2-9D55-448FDED33D79/20190416130424

@alexandrev
Copy link

alexandrev commented Apr 16, 2019

Kubernetes cluster is stuck at:

[15:17:41.539][ApiProxy       ][Info   ] time="2019-04-16T15:17:41+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:42.295][ApiProxy       ][Info   ] time="2019-04-16T15:17:42+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:42.540][ApiProxy       ][Info   ] time="2019-04-16T15:17:42+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:43.293][ApiProxy       ][Info   ] time="2019-04-16T15:17:43+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:43.540][ApiProxy       ][Info   ] time="2019-04-16T15:17:43+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:44.304][ApiProxy       ][Info   ] time="2019-04-16T15:17:44+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:44.575][ApiProxy       ][Info   ] time="2019-04-16T15:17:44+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:45.296][ApiProxy       ][Info   ] time="2019-04-16T15:17:45+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:45.537][ApiProxy       ][Info   ] time="2019-04-16T15:17:45+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:46.294][ApiProxy       ][Info   ] time="2019-04-16T15:17:46+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:46.539][ApiProxy       ][Info   ] time="2019-04-16T15:17:46+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:47.293][ApiProxy       ][Info   ] time="2019-04-16T15:17:47+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:47.548][ApiProxy       ][Info   ] time="2019-04-16T15:17:47+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:48.311][ApiProxy       ][Info   ] time="2019-04-16T15:17:48+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:48.549][ApiProxy       ][Info   ] time="2019-04-16T15:17:48+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:49.294][ApiProxy       ][Info   ] time="2019-04-16T15:17:49+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:49.547][ApiProxy       ][Info   ] time="2019-04-16T15:17:49+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:50.297][ApiProxy       ][Info   ] time="2019-04-16T15:17:50+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:50.544][ApiProxy       ][Info   ] time="2019-04-16T15:17:50+02:00" msg="0/3 system pods running, found labels  but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."
[15:17:51.284][VpnKit         ][Info   ] vpnkit.exe: Expired 256 UDP NAT rules

@mikeparker
Copy link
Contributor

Hi, can you confirm reproduction instructions? In particular are you reporting that kubernetes is starting on a fresh install or did you previously use kubernetes and now you can't turn it off?

@15313974342
Copy link
Author

kubernetes is starting on a fresh install

@alexandrev
Copy link

@mikeparker I have kubernetes working on stable channel and when I change to the edge one it didn't start anymore. I've tried to reset cluster with no luck, also reinstalling Docker Desktop, deleting the Hyper V machine didn't work either...

@alexandrev
Copy link

Also, reset to factory details didn't work.

@alexandrev
Copy link

And also removing .kube folder as well.. @15313974342 how did you do the fresh installation?

@mikeparker
Copy link
Contributor

Can you please clarify what the issue is:

a) You are trying to use Kubernetes and it's not working
b) You are not trying to use Kubernetes and Docker Desktop is incorrectly starting Kubernetes anyway

@alexandrev
Copy link

a) I'm trying to use Kubernetes but it keeps at "Starting" state.

@alexandrev
Copy link

What I'm also seeing is that even when I try to delete everything.. both context docker-desktop and docker-for-desktop are created each time...

@15313974342
Copy link
Author

有可能是防火墙的问题 ,我的这个就是防火墙的问题,关闭防火墙或者
image这种就可以运行

@15313974342 15313974342 reopened this Apr 17, 2019
@rikkigouda
Copy link

rikkigouda commented May 12, 2019

I've got the same issue. Docker logs indicate the following:

[11:45:53.195][ApiProxy ][Info ] time="2019-05-13T11:45:53+12:00" msg="0/3 system pods running, found labels but still waiting for labels k8s-app=kube-dns, component=kube-controller-manager, component=kube-apiserver..."

and Kubernetes cluster installation never finishes.

Any idea what might be causing this? Our boxes use AD. (And no - we cannot turn firewall off, what port requirements are there to allow Docker Desktop to bring up Kubernetes?)

@Sviatik
Copy link

Sviatik commented Jun 21, 2019

This advice to remove C:\ProgramData\DockerDesktop\pki folder and restart docker for windows worked for me.

Source here
#3769

UPD:
I was getting this errors:
[18:24:16.490][ApiProxy ][Info ] time="2019-06-21T18:24:16+03:00" msg="1/3 system pods running, found labels k8s-app=kube-dns but still waiting for labels component=kube-controller-manager, component=kube-apiserver..."

@inech
Copy link

inech commented Jun 25, 2019

@Sviatik Thank you a lot! I've tried millions of different things but only your advice to remove C:\ProgramData\DockerDesktop\pki and restart Docker helped! Now my Kube is green :)

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants