Not able to container images from ACR to Minikube vm

Question

I have created a virtual machine on Azure and I have installed minikube on the VM with VirtualBox. I have created kubectl secret using the instructions in the following link: https://learn.microsoft.com/en-us/azure/container-registry/container-registry-auth-kubernetes I am able to initiate pull request from ACR on the Azure portal:

But the Container is creating for a very long time:

Following is the description of the pod in uestion:

Name:           loginfunctionality-84b59c4464-rr5ss
Namespace:      default
Priority:       0
Node:           minikube/192.168.99.101
Start Time:     Mon, 29 Jun 2020 11:42:01 +0000
Labels:         io.kompose.service=loginfunctionality
                pod-template-hash=84b59c4464
Annotations:    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert
                kompose.version: 1.21.0 (992df58d8)
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/loginfunctionality-84b59c4464
Containers:
  loginfunctionality:
    Container ID:
    Image:          healthcareakscicdacr.azurecr.io/loginfunctionality:latest
    Image ID:
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ASPNETCORE_ENVIRONMENT:   Development
      RedisCacheConnection:     rediscache:6379
      WebApiBaseUrl:            http://20.185.77.158:5018/api/
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f4wfq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-f4wfq:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f4wfq
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  5m3s   default-scheduler  Successfully assigned default/loginfunctionality-84b59c4464-rr5ss to mini
  Normal  Pulling    4m35s  kubelet, minikube  Pulling image "healthcareakscicdacr.azurecr.io/loginfunctionality:latest"
PS C:\DeploymentFiles> kubectl describe pod loginfunctionality-84b59c4464-rr5ss
Name:           loginfunctionality-84b59c4464-rr5ss
Namespace:      default
Priority:       0
Node:           minikube/192.168.99.101
Start Time:     Mon, 29 Jun 2020 11:42:01 +0000
Labels:         io.kompose.service=loginfunctionality
                pod-template-hash=84b59c4464
Annotations:    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert
                kompose.version: 1.21.0 (992df58d8)
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/loginfunctionality-84b59c4464
Containers:
  loginfunctionality:
    Container ID:
    Image:          healthcareakscicdacr.azurecr.io/loginfunctionality:latest
    Image ID:
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ASPNETCORE_ENVIRONMENT:   Development
      RedisCacheConnection:     rediscache:6379
      WebApiBaseUrl:            http://20.185.77.158:5018/api/
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f4wfq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-f4wfq:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f4wfq
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  7m35s  default-scheduler  Successfully assigned default/loginfunctionality-84b59c4464-rr5ss to mini
  Normal  Pulling    7m7s   kubelet, minikube  Pulling image "healthcareakscicdacr.azurecr.io/loginfunctionality:latest"
PS C:\DeploymentFiles> kubectl describe pod loginfunctionality-84b59c4464-rr5ss
Name:           loginfunctionality-84b59c4464-rr5ss
Namespace:      default
Priority:       0
Node:           minikube/192.168.99.101
Start Time:     Mon, 29 Jun 2020 11:42:01 +0000
Labels:         io.kompose.service=loginfunctionality
                pod-template-hash=84b59c4464
Annotations:    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert
                kompose.version: 1.21.0 (992df58d8)
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/loginfunctionality-84b59c4464
Containers:
  loginfunctionality:
    Container ID:
    Image:          healthcareakscicdacr.azurecr.io/loginfunctionality:latest
    Image ID:
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ASPNETCORE_ENVIRONMENT:   Development
      RedisCacheConnection:     rediscache:6379
      WebApiBaseUrl:            http://20.185.77.158:5018/api/
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f4wfq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-f4wfq:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f4wfq
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  11m   default-scheduler  Successfully assigned default/loginfunctionality-84b59c4464-rr5ss to minik
  Normal  Pulling    11m   kubelet, minikube  Pulling image "healthcareakscicdacr.azurecr.io/loginfunctionality:latest"
PS C:\DeploymentFiles> kubectl describe pod loginfunctionality-84b59c4464-rr5ss
Name:           loginfunctionality-84b59c4464-rr5ss
Namespace:      default
Priority:       0
Node:           minikube/192.168.99.101
Start Time:     Mon, 29 Jun 2020 11:42:01 +0000
Labels:         io.kompose.service=loginfunctionality
                pod-template-hash=84b59c4464
Annotations:    kompose.cmd: C:\ProgramData\chocolatey\lib\kubernetes-kompose\tools\kompose.exe convert
                kompose.version: 1.21.0 (992df58d8)
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/loginfunctionality-84b59c4464
Containers:
  loginfunctionality:
    Container ID:
    Image:          healthcareakscicdacr.azurecr.io/loginfunctionality:latest
    Image ID:
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Environment:
      ASPNETCORE_ENVIRONMENT:   Development
      RedisCacheConnection:     rediscache:6379
      WebApiBaseUrl:            http://20.185.77.158:5018/api/
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f4wfq (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  default-token-f4wfq:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-f4wfq
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  16m   default-scheduler  Successfully assigned default/loginfunctionality-84b59c4464-rr5ss to minik
  Normal  Pulling    16m   kubelet, minikube  Pulling image "healthcareakscicdacr.azurecr.io/loginfunctionality:latest"

Please let me know where I am going wrong.

well, since it says `pulling`, not `error pulling` i suspect that something hanged somewhere? did you try restarting the vm? also, did you assign the secret to the pod? — 4c74356b41, Jun 29 '20 at 13:44
yes, I have added imagePullSecrets tag to the yaml which I have used to deploy the service. — Sormita Chakraborty, Jun 29 '20 at 17:10
Restarting the server helped, however though I have added type=LoadBalancer I am not able to expose the service. Though no error in kubectl describe pod or kubectl logs. Any thoughts? — Sormita Chakraborty, Jun 29 '20 at 17:28
@4c74356b41 please note that the service is running fine inside the pod. — Sormita Chakraborty, Jun 29 '20 at 17:30

score 1 · Answer 1 · answered Jun 29 '20 at 17:51

1

Restarting the VM helped resolving the issue.

answered Jun 29 '20 at 17:51

Sormita Chakraborty

1,015
2
19
36

Not able to container images from ACR to Minikube vm

1 Answers1