Not able to create Azure Container Instance with CLI using private image

Question

I can't deploy pod using private image (ACR) using CLI and yaml file.

Deploying from registry directly using either az container or kubectl run does work however.

Pod status:

  "containers": [
    {

            "count": 3,
            "firstTimestamp": "2017-08-26T07:31:36+00:00",
            "lastTimestamp": "2017-08-26T07:32:20+00:00",
            "message": "Failed: Failed to pull image \"ucont01.azurecr.io/unreal-deb\": rpc error: code 2 desc Error: im age unreal-deb:latest not found",
            "type": "Warning"
          },
        ],
      },

Yaml file:

apiVersion: v1
kind: Pod
metadata:
  generateName: "game-"
  namespace: default
spec:
  nodeName: aci-connector
  dnsPolicy: ClusterFirst
  restartPolicy: Never
  containers:
    - name: unreal-dev-server
      image: ucont01.azurecr.io/unreal-deb
      imagePullPolicy: Always
      ports:
      - containerPort: 7777
        protocol: UDP
  imagePullSecrets:
    - name: registrykey

Lachlan Evenson · Accepted Answer · 2017-08-28 20:12:39Z

3

Unfortunately the aci-connector-k8s doesn't currently support images from private repositories. There is an issue open to add support but it's not currently implemented.

https://github.com/Azure/aci-connector-k8s/issues/35

answered Aug 28, 2017 at 20:12

Lachlan Evenson

1065 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Jason Ye · Accepted Answer · 2017-08-28 07:18:54Z

1

According to your description, could you please check your repositories via Azure portal, like this:

Use your YAML, it work for me:

apiVersion: v1
kind: Pod
metadata:
  generateName: "game-"
  namespace: default
spec:
  nodeName: k8s-agent-379980cb-0
  dnsPolicy: ClusterFirst
  restartPolicy: Never
  containers:
    - name: unreal-dev-server
      image: jasontest.azurecr.io/samples/nginx
      imagePullPolicy: Always
      ports:
      - containerPort: 7777
        protocol: TCP
  imagePullSecrets:
    - name: secret1

Here is the screenshot:

Here is my secret:

jason@k8s-master-379980CB-0:~$ kubectl get secret
NAME                  TYPE                                  DATA      AGE
default-token-865dj   kubernetes.io/service-account-token   3         1h
secret1               kubernetes.io/dockercfg               1         47m

answered Aug 28, 2017 at 7:18

Jason Ye

14k2 gold badges20 silver badges28 bronze badges

1 Comment

Jason Ye Over a year ago

Does that work for you? please let me know if you need more help:)

Siva G · Accepted Answer · 2017-08-26 14:46:27Z

0

If the credentials (corresponding to registrykey) are incorrect, you may get 'image not found' error, though the image exists. you may want to verify the registrykey credentials again..

answered Aug 26, 2017 at 14:46

Siva G

212 bronze badges

1 Comment

Łukasz Baran Over a year ago

I added another secret point to the same registry and it still doesn't work. I can run images from the same registry using kubectl run --image=. I'm fairly positive that credentials are ok then.

Collectives™ on Stack Overflow

Not able to create Azure Container Instance with CLI using private image

3 Answers 3

Comments

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related