Forum Discussion

dannybhar's avatar
dannybhar
Copper Contributor
Oct 29, 2021

AKS error

I have docker image in ACS and I am trying to pull it in YAML to put in replicaset for AKS.

But getting following error

 

fault-scheduler Successfully assigned default/x-depl1-7954d9c545-h2x7c to aks-nodepool1-33798810-vmss000001
Normal Pulling 19m (x4 over 21m) kubelet Pulling image "xxx"
Warning Failed 19m (x4 over 21m) kubelet Failed
to pull image "XXX": rpc error: code = Unknown desc = failed to pull and unpack image "xxx: failed to resolve reference "XXX": failed to authorize: failed to fetch anonymous token: unexpected
status: 401 Unauthorized
Warning Failed 19m (x4 over 21m) kubelet Error:
ErrImagePull
Normal BackOff 19m (x6 over 21m) kubelet Back-off pulling image "xxx"
Warning Failed 80s (x87 over 21m) kubelet Error:
ImagePullBackOff

Here is my template,can somebody help me?

template:
metadata:
labels:
app: sim
spec:
imagePullSecrets:
- name: xx-cred
containers:
- name: sim
image: xxx

1 Reply

  • LukeJMadden's avatar
    LukeJMadden
    Brass Contributor
    Mar 30, 2023
    Hey dannybhar, second question I have seen form you, having a rough time?

    It looks like you are encountering an error pulling a Docker image in AKS. The error message indicates that the image pull failed due to authentication issues.

    Here are some steps you can try to resolve the issue:

    Verify that the image name and tag are correct: Double-check that the image name and tag you are trying to pull are correct. Make sure that the image is available in your container registry and that you have permissions to access it.

    Check your image pull secret: Ensure that you have created a valid image pull secret and that it is correctly specified in your YAML file. Verify that the secret has the correct credentials to access your container registry.

    Check your cluster network configuration: Ensure that your AKS cluster has the necessary network configuration to pull images from your container registry. You may need to configure a private endpoint or allow traffic to your container registry in your network security groups.

    Verify that your cluster is up to date: Ensure that your AKS cluster is running the latest version of Kubernetes and AKS.

    Check your Azure subscription permissions: Ensure that you have the necessary permissions in your Azure subscription to pull images from your container registry.

    I hope this helps! Let me know if you have any further questions.

    Kind regards,

    Luke Madden

Resources