microk8s拉取镜像，卡在ContainerCreating状态

如中所述doc https://microk8s.io/docs/working (based on https://stackoverflow.com/questions/55549522/how-to-configure-kubernetes-microk8s-to-use-local-docker-images).

我使用 Ubuntu 作为主机操作系统。

docker --version

Docker 版本 18.09.6，内部版本 481bc77

microk8s 1.14/beta

启用本地注册表microk2s:

microk8s.enable registry

检查：

watch microk8s.kubectl get all --all-namespaces

容器注册表 pod/registry-577986746b-v8xqc 1/1 运行 0 36m

Then:

Edit:

sudo vim /etc/docker/daemon.json

添加此内容：

{
  "insecure-registries" : ["127.0.0.1:32000"]
}

Restart:

sudo systemctl restart docker

仔细检查，看看是否应用了不安全：

docker info | grep -A 2 Insecure

Insecure Registries:
 127.0.0.1:32000
 127.0.0.0/8
WARNING: No swap limit support

Tag:

docker tag my-registry/my-services/my-service:0.0.1-SNAPSHOT 127.0.0.1:32000/my-service

检查：

docker images

127.0.0.1:32000/my-service 最新 e68f8a7e4675 19 小时前 540MB

Pushing:

docker push 127.0.01:32000/my-service

我在这里看到我的图片：http://127.0.0.1:32000/v2/_catalog http://127.0.0.1:32000/v2/_catalog

In deployment-local.yml我现在有了正确的图像：

...spec:
  containers:
    - name: my-service-backend
      image: 127.0.0.1:32000/my-service
      imagePullPolicy: Always ...

然后申请：

envsubst < ./.local/deployment-local.yml | microk8s.kubectl apply -f -

I see: ContainerCreating

By: microk8s.kubectl describe pods my-service-deployment-f85d5dcd5-cmd5

在活动部分：

Events:
  Type     Reason     Age                 From                     Message
  ----     ------     ----                ----                     -------
  Normal   Scheduled  107s                default-scheduler        Successfully assigned default/my-service-deployment-f85d5dcd5-z75tr to my-desktop
  Normal   Pulling    25s (x4 over 106s)  kubelet, my-desktop  Pulling image "127.0.0.1:32000/my-service"
  Warning  Failed     25s (x4 over 106s)  kubelet, my-desktop  Failed to pull image "127.0.0.1:32000/my-service": rpc error: code = Unknown desc = failed to resolve image "127.0.0.1:32000/my-service:latest": no available registry endpoint: failed to do request: Head https://127.0.0.1:32000/v2/my-service/manifests/latest: http: server gave HTTP response to HTTPS client
  Warning  Failed     25s (x4 over 106s)  kubelet, my-desktop  Error: ErrImagePull
  Normal   BackOff    10s (x5 over 105s)  kubelet, my-desktop  Back-off pulling image "127.0.0.1:32000/my-service"
  Warning  Failed     10s (x5 over 105s)  kubelet, my-desktop  Error: ImagePullBackOff

看来我的服务被困在那里。

问： 可能是什么原因？

UPDATE:全部更改为localhost有帮助，这意味着我现在可以在浏览器中看到：http://localhost:32000/v2/_catalog http://localhost:32000/v2/_catalog .

{"repositories":["my-service"]}

但它只在 Firefox 中有效......奇怪。在 chrome 中正在等待..

Still:

Events:
  Type     Reason          Age                    From                    Message
  ----     ------          ----                   ----                    -------
  Normal   Scheduled       161m                   default-scheduler       Successfully assigned default/my-service-deployment-6d4c5587df-72xvd to my-laptop
  Normal   Pulling         160m (x4 over 161m)    kubelet, my-laptop  Pulling image "localhost/my-service"
  Warning  Failed          160m (x4 over 161m)    kubelet, my-laptop  Failed to pull image "localhost/my-service": rpc error: code = Unknown desc = failed to resolve image "localhost/my-service:latest": no available registry endpoint: failed to do request: Head https://localhost/v2/my-service/manifests/latest: dial tcp 127.0.0.1:443: connect: connection refused
  Warning  Failed          160m (x4 over 161m)    kubelet, my-laptop  Error: ErrImagePull
  Warning  Failed          159m (x6 over 161m)    kubelet, my-laptop  Error: ImagePullBackOff
  Normal   BackOff         131m (x132 over 161m)  kubelet, my-laptop  Back-off pulling image "localhost/my-service"
  Normal   SandboxChanged  22m                    kubelet, my-laptop  Pod sandbox changed, it will be killed and re-created.
  Normal   Pulling         21m (x4 over 22m)      kubelet, my-laptop  Pulling image "localhost/my-service"
  Warning  Failed          21m (x4 over 22m)      kubelet, my-laptop  Failed to pull image "localhost/my-service": rpc error: code = Unknown desc = failed to resolve image "localhost/my-service:latest": no available registry endpoint: failed to do request: Head https://localhost/v2/my-service/manifests/latest: dial tcp 127.0.0.1:443: connect: connection refused
  Warning  Failed          21m (x4 over 22m)      kubelet, my-laptop  Error: ErrImagePull
  Warning  Failed          20m (x6 over 22m)      kubelet, my-laptop  Error: ImagePullBackOff
  Normal   BackOff         2m22s (x87 over 22m)   kubelet, my-laptop  Back-off pulling image "localhost/my-service"

似乎它尝试通过 https 连接..

--

好吧..必须添加 yml 图像的端口：部分。会接受下面的答案。谢谢。

在 microk8s 之间有很大的不同本地主机 and 127.0.0.1。正如你所提到的，你是基于this https://stackoverflow.com/questions/55549522/how-to-configure-kubernetes-microk8s-to-use-local-docker-images堆栈案例和用户正在使用本地主机.

这里的主要问题是错误no available registry endpoint: failed to do request:。这意味着 microk8s 找不到端点。

如果您在下面运行command，您将得到相同的输出

$ cat /var/snap/microk8s/current/args/containerd-template.toml | grep endpoint

endpoint = ["https://registry-1.docker.io"]
endpoint = ["http://localhost:32000"]

正如您在 microk8s 端点中看到的那样本地主机不是 127.0.0.1

请更改deployment-local.yaml中的图像

...spec:
  containers:
    - name: my-service-backend
      image: localhost/my-service
      imagePullPolicy: Always ...

如果您会遇到任何其他问题，请告诉我。

就我而言，我不需要使用 localhost 再次标记和推送图像，只需要更改 YAML。