Jan 7, 2018 - Docker for Mac now ships with Kubernetes built-in! Let's explore why this matters, a history of developer tooling & my first impressions as I kick. Kubernetesを内蔵したDocker for Macがリリースされたらしいので、試してみた kubectlコマンドでkubernetes-dashboardのデプロイ、docker stackコマンドでmetabaseをデプロイしてみた. • [ x] I have tried with the latest version of my channel (Stable or Edge) • [ x] I have uploaded Diagnostics • Diagnostics ID: 804B8977-06D2-4E2A-BB3E-10FBBA99D1F9/20149 Expected behavior Within a few minutes of starting Docker for Mac, Kubernetes should be available. Actual behavior After several hours, it is still 'starting' Information • macOS Version: 10.13.5 Diagnostic logs (Uploaded as 804B8977-06D2-4E2A-BB3E-10FBBA99D1F9/20149) Steps to reproduce the behavior • I've quit Docker, rebooted, and started it again, with the same result. I have the same problem when update to the version 18.05.0-ce-mac67 (25042). • I can use kubectl commands even though Docker for mac is showing Kubernetes is starting. • I cannot stop Kubernetes from Preferences. -> Kubernetes. • External IP is not attached to LB (only showing ) though I have waited for 20 min. • Previous version ( 18.05.0-ce-mac66) attached localhost as External IP to LB • This version only shows and cURL command like curl returns error: curl: (7) Failed to connect to localhost port 80: Connection refused even though I could use this on the previous version. $ kgs NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE crazy-greyhound-nginx-ingress-controller LoadBalancer 10.96.142.184 80:31157/TCP,443:30351/TCP 27m crazy-greyhound-nginx-ingress-default-backend ClusterIP 10.103.196.198 80/TCP 27m. Diagnostic logs: 2E0B1819-92A4-408C-9548-B52A29AAF12-214950. I also have this issue. Kubernetes worked fine one time, but after I had to reboot, it got stuck in 'Kubernetes is starting'. I tried these steps: • Reboot again • Reset Kubernetes • Reset Disk • Reset to factory defaults • Uninstall/Reinstall • Uninstall/Install edge release • Uninstall/Reinstall edge with manually removing stuff smelling like docker/kubernetes from my home directory But it still won't start. $ kubectl cluster-info Kubernetes master is running at To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. ![]() ![]() Unable to connect to the server: EOF $ kubectl cluster-info dump Unable to connect to the server: EOF. Thanks for your update. I suspect the earlier EOF error is expected, because the host software polls localhost:6443 for the kubernetes API, and I would expect an EOF from the port forwarder until the API server binds the port in the container. We should probably stop logging these 'expected' errors. The curl is interesting -- it looks like the API server is responding correctly. Could you try: $ kubectl --context docker-for-desktop get nodes NAME STATUS ROLES AGE VERSION docker-for-desktop Ready master 1d v1.11.2 -- sometimes the reason kubectl commands fail is because the wrong context is being used, so it's good to be specific.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |