如何使用Kubernetespod修复ImagePullBackOff?

时间:2019-05-15 15:05:51

标签: kubernetes

我5个小时前创建了一个广告连播。现在出现错误:拉回 这些是来自describe pod的事件

Events:
  Type     Reason       Age                      From               Message
  ----     ------       ----                     ----               -------
  Normal   Scheduled    4h51m                    default-scheduler  Successfully assigned default/nodehelloworld.example.com to minikube
  Normal   Pulling      4h49m (x4 over 4h51m)    kubelet, minikube  pulling image "milenkom/docker-demo"
  Warning  Failed       4h49m (x4 over 4h51m)    kubelet, minikube  Failed to pull image "milenkom/docker-demo": rpc error: code = Unknown desc = Error response from daemon: manifest for milenkom/docker-demo:latest not found
  Warning  Failed       4h49m (x4 over 4h51m)    kubelet, minikube  Error: ErrImagePull
  Normal   BackOff      4h49m (x6 over 4h51m)    kubelet, minikube  Back-off pulling image "milenkom/docker-demo"
  Warning  Failed       4h21m (x132 over 4h51m)  kubelet, minikube  Error: ImagePullBackOff
  Warning  FailedMount  5m13s                    kubelet, minikube  MountVolume.SetUp failed for volume "default-token-zpl2j" : couldn't propagate object cache: timed out waiting for the condition
  Normal   Pulling      3m34s (x4 over 5m9s)     kubelet, minikube  pulling image "milenkom/docker-demo"
  Warning  Failed       3m32s (x4 over 5m2s)     kubelet, minikube  Failed to pull image "milenkom/docker-demo": rpc error: code = Unknown desc = Error response from daemon: manifest for milenkom/docker-demo:latest not found
  Warning  Failed       3m32s (x4 over 5m2s)     kubelet, minikube  Error: ErrImagePull
  Normal   BackOff      3m5s (x6 over 5m1s)      kubelet, minikube  Back-off pulling image "milenkom/docker-demo"
  Warning  Failed       3m5s (x6 over 5m1s)      kubelet, minikube  Error: ImagePullBackOff

我桌面上的图像

docker images
REPOSITORY                  TAG                 IMAGE ID            CREATED             SIZE
milenkom/docker-demo        tagname             08d27ff00255        6 hours ago         659MB

遵循Max和Shanica的建议,我在标记时一团糟

docker tag 08d27ff00255 docker-demo:latest

工作正常,但是当我尝试 docker push docker-demo:latest 该推送指的是存储库[docker.io/library/docker-demo]

e892b52719ff: Preparing 
915b38bfb374: Preparing 
3f1416a1e6b9: Preparing 
e1da644611ce: Preparing 
d79093d63949: Preparing 
87cbe568afdd: Waiting 
787c930753b4: Waiting 
9f17712cba0b: Waiting 
223c0d04a137: Waiting 
fe4c16cbf7a4: Waiting 
denied: requested access to the resource is denied

尽管我已登录

输出Docker检查映像08d27ff00255

[
    {
        "Id": "sha256:08d27ff0025581727ef548437fce875d670f9e31b373f00c2a2477f8effb9816",
        "RepoTags": [
            "docker-demo:latest",
            "milenkom/docker-demo:tagname"
        ],

为什么现在无法分配吊舱?

1 个答案:

答案 0 :(得分:3)

manifest for milenkom/docker-demo:latest not found

好像您要拉取的图像中没有最新标签:https://hub.docker.com/r/milenkom/docker-demo/tags

尝试一些现有图像。

UPD(基于问题更新):

  1. docker push milenkom / docker-demo:tagname
  2. 更新k8s窗格以指向milenkom/docker-demo:tagname