一旦我安裝了 docker 并運行它，我也安裝了 kubernetes，然后我安裝了 minikube 并啟動了它。
當我得到這些結果時，我通過kubectl create deployment --image=imageName imageName創建了一些部署，我想要一個解決方案，我試圖理解 kubernetes 錯誤，但我沒有，當我得到我的 pod 時，我得到了這些：
PS C:\Users\ahmed> kubectl get pods
NAME READY STATUS RESTARTS AGE
depl-im-54cbb55ccb-mjl6q 0/1 ErrImagePull 0 86m
ngnix-app-8d489bb64-tlvrn 0/1 ErrImagePull 0 15h
當描述一個（如 'ngnix-app-8d489bb64-tlvrn'）時，我得到：
PS C:\Users\ahmed> kubectl describe pod depl-im-54cbb55ccb-mjl6q
Name:depl-im-54cbb55ccb-mjl6q
Namespace: default
Priority: 0
Node: minikube/192.168.49.2
Start Time: Sat, 01 Jan 2022 12:26:05 0200
Labels: app=depl-im
pod-template-hash=54cbb55ccb
Annotations: <none>
Status: Pending
IP: 172.17.0.4
IPs:
IP: 172.17.0.4
Controlled By: ReplicaSet/depl-im-54cbb55ccb
Containers:
depl-im:
Container ID:
Image: depl-im
Image ID:
Port: <none>
Host Port: <none>
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-b9f8h (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-b9f8h:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 86m default-scheduler Successfully assigned default/depl-im-54cbb55ccb-mjl6q to minikube
Normal Pulling 84m (x4 over 86m) kubelet Pulling image "depl-im"
Warning Failed 84m (x4 over 86m) kubelet Failed to pull image "depl-im": rpc error: code = Unknown desc = Error response from daemon: pull access denied for depl-im, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Warning Failed 84m (x4 over 86m) kubelet Error: ErrImagePull
Warning Failed 84m (x6 over 86m) kubelet Error: ImagePullBackOff
Normal BackOff 56m (x128 over 86m) kubelet Back-off pulling image "depl-im"
Normal SandboxChanged 114s kubelet Pod sandbox changed, it will be killed and re-created.
Normal BackOff 33s (x2 over 61s) kubelet Back-off pulling image "depl-im"
Warning Failed 33s (x2 over 61s) kubelet Error: ImagePullBackOff
Normal Pulling 18s (x3 over 80s) kubelet Pulling image "depl-im"
Warning Failed 15s (x3 over 62s) kubelet Failed to pull image "depl-im": rpc error: code = Unknown desc = Error response from daemon: pull access denied for depl-im, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Warning Failed 15s (x3 over 62s) kubelet Error: ErrImagePull
uj5u.com熱心網友回復：
如果 kubernetes 嘗試拉取的此映像由私有映像存盤庫托管，則您需要在部署部署/pod 的同一 kubernetes 命名空間中放置一個包含憑據的密鑰。
然后，使用
imagePullSecrets:
- name: secret-name
在您的部署規范中。
供參考：https : //kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
如果您嘗試在 Kubernetes 中使用本地構建的 docker 鏡像，請查看以下內容：https ://medium.com/swlh/how-to-run-locally-built-docker-images-in-kubernetes-b28fbc32cc1d
uj5u.com熱心網友回復：
請使用以下命令首先登錄您的影像所在的存盤庫：
#docker login `repository url` -u `username` -p `password`
然后嘗試手動獲取：
#docker pull `imagename`
轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/401719.html
標籤：Kubernetes kubectl 迷你酷