+1 k8s is starting

执行 load_images.sh成功，无异常。

重启啥的都是starting，在线求助 🙏🙏🙏

• macOS Catalina 10.15.7
• docker desktop 2.4.0.0(48506)
• docker engine 19.03.13
• docker compose 1.27.4
• k8s v1.18.8

Originally posted by @tanpenggood in #37 (comment)

docker for mac engine:19.03.3 . 执行./load_images.sh k8s enable一直加载不了

error info:

-rwxr-xr-x  1 meixin  staff   271B Dec  1 14:55 load_images.sh
➜  k8s-docker-for-mac git:(master) ✗ ./load_images.sh 
images found.
v1.10.3: Pulling from google_containers/kube-proxy-amd64
e22465b204dc: Pulling fs layer 
7e16ccc2c5be: Pulling fs layer 
a8cafb53097b: Pulling fs layer 
error pulling image configuration: received unexpected HTTP status: 503 Service Unavailable
Error response from daemon: No such image: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy-amd64:v1.10.3
Error: No such image: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-proxy-amd64:v1.10.3
v1.10.3: Pulling from google_containers/kube-controller-manager-amd64
032c9e83eacf: Pulling fs layer 
15eed34a755a: Pulling fs layer 
error pulling image configuration: received unexpected HTTP status: 503 Service Unavailable
Error response from daemon: No such image: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager-amd64:v1.10.3
Error: No such image: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-controller-manager-amd64:v1.10.3
v1.10.3: Pulling from google_containers/kube-scheduler-amd64
032c9e83eacf: Pulling fs layer 
70ade0f3cd17: Pulling fs layer 
error pulling image configuration: received unexpected HTTP status: 503 Service Unavailable
Error response from daemon: No such image: regi...................

求更新连接~

原来的
k8s.gcr.io/etcd:3.4.3-0=gotok8s/etcd:3.4.13-0
正确的
k8s.gcr.io/etcd:3.4.13-0=gotok8s/etcd:3.4.13-0

• Surge
• Shadowsocks

可以利用Surge为其他机器开启代理。 参考: maguowei/gotok8s#4

按照指南，mac下通过官方的docker客户端，部署 Kubernetes dashboard 出错

 ~> kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml
secret "kubernetes-dashboard-certs" configured
serviceaccount "kubernetes-dashboard" configured
service "kubernetes-dashboard" configured
unable to decode "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": no kind "Role" is registered for version "rbac.authorization.k8s.io/v1"
unable to decode "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": no kind "RoleBinding" is registered for version "rbac.authorization.k8s.io/v1"
unable to decode "https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml": no kind "Deployment" is registered for version "apps/v1beta2"

这个是怎么解决的？

还有很奇怪的是，docker客户端里k8s的状态一直是running，在它的组件如apiserver等容器的日志里面没有看到异常，是不是缺乏什么东西？

已自己解决

步骤如下：
替换vim images

k8s.gcr.io/kube-proxy:v1.19.3=gotok8s/kube-proxy:v1.19.3
k8s.gcr.io/kube-controller-manager:v1.19.3=gotok8s/kube-controller-manager:v1.19.3
k8s.gcr.io/kube-scheduler:v1.19.3=gotok8s/kube-scheduler:v1.19.3
k8s.gcr.io/kube-apiserver:v1.19.3=gotok8s/kube-apiserver:v1.19.3
k8s.gcr.io/coredns:1.7.0=gotok8s/coredns:1.7.0
k8s.gcr.io/pause:3.2=gotok8s/pause:3.2
k8s.gcr.io/etcd:3.4.13-0=gotok8s/etcd:3.4.13-0

之后./load_images.sh

然后docker-desktop软件软件中 enable Kubernetes

过几分钟就ok了

目前的正式release是k8s v1.15.5。这个没什么问题，但是etcd，coredns这些的版本怎么找

docker 和 Kubernetes都启动了 用kubectl cluster-info 命令查看显示：
from server (InternalError): an error on the server ("") has prevented the request from succeeding (get nodes)

请问一下这个是什么原因导致的？

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Unable to connect to the server: x509: certificate is valid for docker-for-desktop, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, host.docker.internal, not kubernetes.docker.internal

dockerhub 的速度也变得感人，很多镜像加速也无法使用了

目前可用的镜像加速服务:

• 阿里云-镜像加速器

上周自动升级后，就一直"Kubernetes is starting"。 应该都是最新版。
帮忙分析下啥原因？ 谢谢。

Mac OS Mojave 10.14.6
Version 2.1.2.0(38030)
Channel edge
Engine 19.03.2
Kubernetes v1.14.6

错误日志：
2019-09-16 15:12:07.881411+0800 localhost com.docker.driver.amd64-linux[6156]: (libsystem_info.dylib) [com.apple.network.libinfo:getaddrinfo] nat64_v4_requires_synthesis(127.0.0.1) == false 2019-09-16 15:12:07.883410+0800 localhost com.docker.driver.amd64-linux[6156]: Cannot list nodes: Get https://kubernetes.docker.internal:6443/api/v1/nodes: EOF

感觉关键步骤完全没写明白。。。。

环境

macos 10.15

docker edge 1.16.5

解决办法

修改了镜像 registly-mirror后，再次执行./load_images.sh
然后勾选启用k8s,前两项，第三项不需要勾选。

apply，然后网速好等待3分钟即可。（本人没有开翻墙，千M电信宽带，查的网线）

一直卡住怎么办？

1. 检查你的wifi网速，推荐使用网线

2. 不要开ss加速了，用国内镜像源了，你还加速？

3. 你修改镜像源后，到底有没有再次执行./load_images.sh？

4. 如果你做到了上面这些，依然有问题，请你换个网络环境/换电脑/试试看

像我的机器上目前是最新的V2.2.0.3，对应的k8s版本显示的是v1.15.5。
我修改了load_images.sh为1.15.5， 但是执行后发现k8s依然一直是starting中，应该还是镜像不对应导致的。

如果能查到当前版本的k8s需要的镜像是哪个版本的，或许这个问题就可以迎刃而解。
所以有什么方法吗？

不再依赖阿里的镜像同步源

-> https://github.com/gotok8s/gotok8s/tree/master/content/setup/kind

找不到镜像

$ ./load_images.sh
images found.
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Error response from daemon: No such image: gotok8s/kube-controller-manager:latest
Error: No such image: gotok8s/kube-controller-manager
Using default tag: latest
Error response from daemon: manifest for gotok8s/kube-apiserver:latest not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/kube-apiserver:latest
Error: No such image: gotok8s/kube-apiserver
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: gotok8s/coredns:latest
Error: No such image: gotok8s/coredns
Using default tag: latest
Error response from daemon: manifest for gotok8s/pause:latest not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/pause:latest
Error: No such image: gotok8s/pause
Error response from daemon: Get https://registry-1.docker.io/v2/gotok8s/kube-proxy/manifests/v1.16.5: Get https://auth.docker.io/token?scope=repository%3Agotok8s%2Fkube-proxy%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Error response from daemon: No such image: gotok8s/kube-proxy:v1.16.5
Error: No such image: gotok8s/kube-proxy:v1.16.5
3.3.15-0: Pulling from gotok8s/etcd
Digest: sha256:37a8acab63de5556d47bfbe76d649ae63f83ea7481584a2be0dbffb77825f692
Status: Downloaded newer image for gotok8s/etcd:3.3.15-0
docker.io/gotok8s/etcd:3.3.15-0
Untagged: gotok8s/etcd:3.3.15-0
Untagged: gotok8s/etcd@sha256:37a8acab63de5556d47bfbe76d649ae63f83ea7481584a2be0dbffb77825f692
$ docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
k8s.gcr.io/kube-proxy       v1.16.5             0ee1b8a3ebe0        2 months ago        82.7MB
k8s.gcr.io/kube-scheduler   v1.16.5             b4d073a9efda        2 months ago        83.5MB
k8s.gcr.io/etcd             3.3.15-0            b2756210eeab        7 months ago        247MB

registry-mirrors已经改了，但还是出现了上面的错误。而且我把images里的tag信息也都去掉了，也还是如此。

请问怎么修改service-node-port-range这个的值呢

detail error msg:

root@DESKTOP-LQQ3Q0F:~/gotok8s# kubeadm config images pull --config init.yml
[config/images] Pulled gotok8s/kube-apiserver:v1.21.0
[config/images] Pulled gotok8s/kube-controller-manager:v1.21.0
[config/images] Pulled gotok8s/kube-scheduler:v1.21.0
[config/images] Pulled gotok8s/kube-proxy:v1.21.0
[config/images] Pulled gotok8s/pause:3.4.1
[config/images] Pulled gotok8s/etcd:3.4.13-0
failed to pull image "gotok8s/coredns/coredns:v1.8.0": output: Error response from daemon: pull access denied for gotok8s/coredns/coredns, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

Docker **官方镜像加速 已经不可用 docker/docs#8793

可用下列镜像地址替代

• https://dockerhub.azk8s.cn
• https://mirror.ccs.tencentyun.com

ref:

• https://github.com/Azure/container-service-for-azure-china/blob/master/aks/README.md#22-container-registry-proxy
• http://mirror.azk8s.cn/help/docker-registry-proxy-cache.html

M1的不能用啊 ，M1的如何使用呢

只有这个2.1.4.0的版本能用 搞了好久 给别人提个醒。。。。

问题描述

https://registry.docker-cn.com已经无法访问

建议方案

将https://registry.docker-cn.com改为https://www.docker-cn.com

MacOS Catalina 10.15.7
docker-desktop 3.5.2.18
docker engine v20.10.7
kubernetes: v1.21.2

images和kubernetes版本一致，不知道为什么启动失败，不知该如何解决？

系统版本 macOS Catalina 10.15.7
Docker Desktop版本 Channel:edge Version:2.4.2.0(48975)

这是第二步的执行结果
➜ k8s-docker-for-mac git:(master) ./load_images.sh images found. v1.19.2: Pulling from gotok8s/kube-proxy Digest: sha256:a5e646dc3b90ff921bcabd25f42af79b0524402485ebb3a81a15d65cd858d1ed Status: Downloaded newer image for gotok8s/kube-proxy:v1.19.2 docker.io/gotok8s/kube-proxy:v1.19.2 Untagged: gotok8s/kube-proxy:v1.19.2 Untagged: gotok8s/kube-proxy@sha256:a5e646dc3b90ff921bcabd25f42af79b0524402485ebb3a81a15d65cd858d1ed v1.19.2: Pulling from gotok8s/kube-controller-manager Digest: sha256:f8c271e12218a32eecd39ffe98f9e47dae6554fc0ca30071bf32280da00b02dd Status: Downloaded newer image for gotok8s/kube-controller-manager:v1.19.2 docker.io/gotok8s/kube-controller-manager:v1.19.2 Untagged: gotok8s/kube-controller-manager:v1.19.2 Untagged: gotok8s/kube-controller-manager@sha256:f8c271e12218a32eecd39ffe98f9e47dae6554fc0ca30071bf32280da00b02dd v1.19.2: Pulling from gotok8s/kube-scheduler Digest: sha256:67076f919fd65602ba69219d2a630737cd826459d866d85f106b36f4857505d0 Status: Downloaded newer image for gotok8s/kube-scheduler:v1.19.2 docker.io/gotok8s/kube-scheduler:v1.19.2 Untagged: gotok8s/kube-scheduler:v1.19.2 Untagged: gotok8s/kube-scheduler@sha256:67076f919fd65602ba69219d2a630737cd826459d866d85f106b36f4857505d0 v1.19.2: Pulling from gotok8s/kube-apiserver Digest: sha256:b119baef2a60b537c264c0ea009f63095169af089e1a36fb4167693f1b60cd1e Status: Downloaded newer image for gotok8s/kube-apiserver:v1.19.2 docker.io/gotok8s/kube-apiserver:v1.19.2 Untagged: gotok8s/kube-apiserver:v1.19.2 Untagged: gotok8s/kube-apiserver@sha256:b119baef2a60b537c264c0ea009f63095169af089e1a36fb4167693f1b60cd1e 1.6.7: Pulling from gotok8s/coredns Digest: sha256:695a5e109604331f843d2c435f488bf3f239a88aec49112d452c1cbf87e88405 Status: Downloaded newer image for gotok8s/coredns:1.6.7 docker.io/gotok8s/coredns:1.6.7 Untagged: gotok8s/coredns:1.6.7 Untagged: gotok8s/coredns@sha256:695a5e109604331f843d2c435f488bf3f239a88aec49112d452c1cbf87e88405 3.2: Pulling from gotok8s/pause Digest: sha256:4a1c4b21597c1b4415bdbecb28a3296c6b5e23ca4f9feeb599860a1dac6a0108 Status: Downloaded newer image for gotok8s/pause:3.2 docker.io/gotok8s/pause:3.2 Untagged: gotok8s/pause:3.2 Untagged: gotok8s/pause@sha256:4a1c4b21597c1b4415bdbecb28a3296c6b5e23ca4f9feeb599860a1dac6a0108 3.4.3-0: Pulling from gotok8s/etcd Digest: sha256:4198ba6f82f642dfd18ecf840ee37afb9df4b596f06eef20e44d0aec4ea27216 Status: Downloaded newer image for gotok8s/etcd:3.4.3-0 docker.io/gotok8s/etcd:3.4.3-0 Untagged: gotok8s/etcd:3.4.3-0 Untagged: gotok8s/etcd@sha256:4198ba6f82f642dfd18ecf840ee37afb9df4b596f06eef20e44d0aec4ea27216

Error: could not find a ready tiller pod

原因是作者更新了 tiller到 2.14.1
helm init的时候，还是去找 2.14.0

Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.14.0": rpc error: code = Unknown desc = Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

需要手工修改 tiller-deploy 里面的 "image": "gcr.io/kubernetes-helm/tiller:v2.14.0" 成 "image": "gcr.io/kubernetes-helm/tiller:v2.14.1" 就可以使用了

Error response from daemon: manifest for gotok8s/kube-proxy:v1.14.7 not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/kube-proxy:v1.14.7
Error: No such image: gotok8s/kube-proxy:v1.14.7
Error response from daemon: manifest for gotok8s/kube-controller-manager:v1.14.7 not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/kube-controller-manager:v1.14.7
Error: No such image: gotok8s/kube-controller-manager:v1.14.7
Error response from daemon: manifest for gotok8s/kube-scheduler:v1.14.7 not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/kube-scheduler:v1.14.7
Error: No such image: gotok8s/kube-scheduler:v1.14.7
Error response from daemon: manifest for gotok8s/kube-apiserver:v1.14.7 not found: manifest unknown: manifest unknown
Error response from daemon: No such image: gotok8s/kube-apiserver:v1.14.7
Error: No such image: gotok8s/kube-apiserver:v1.14.7

当前只同步了最新的 edge 版本对应的kubernetes 依赖镜像，须增加stable版本的支持

现象如图：

./load_images.sh

这一步在哪里执行？点完哪一个按钮然后在哪里执行呢？

https://github.com/kubernetes/dashboard/releases/tag/v1.10.0