[Kubernetes] "Image can't be pulled" error from while pulling image from private insecure registry

DevOps
#1

Kubernetes pull image from private insecure registry

I have a private insecure registry configured with images being pushed to it successfully. I am trying to deploy a kubernetes deployment and service for that image but I get the below error for the pod
Error from server (BadRequest): container "my-app" in pod "my-deployment-695b96dc66-4mzdn" is waiting to start: image can't be pulled
Detailed error with describe command is
Failed to pull image "C6-PU-POC-ND-SH-A-APS-3:5000/temp/leads:latest": rpc error: code = Unknown desc = failed to pull and unpack image "C6-PU-POC-ND-SH-A-APS-3:5000/temp/leads:latest": failed to resolve reference "C6-PU-POC-ND-SH-A-APS-3:5000/temp/leads:latest": failed to do request: Head "[https://C6-PU-POC-ND-SH-A-APS-3:5000/v2/temp/leads/manifests/latest](https://C6-PU-POC-ND-SH-A-APS-3:5000/v2/temp/leads/manifests/latest)": http: server gave HTTP response to HTTPS client
docker pull works with this command - I have daemon.json configured with insecure-registries
docker pull C6-PU-POC-ND-SH-A-APS-3:5000/temp/leads:latest
Any idea what could be wrong?

Thanks.

#2 
kind: Deployment
metadata:
  name: orion-leads-deployment
  namespace: oleads
spec:
  replicas: 1
  selector:
    matchLabels:
      app: orion-leads-app
  template:
    metadata:
      labels:
        app: orion-leads-app
    spec:
      containers:
        - name: orion-leads-app
          image: C6-PU-POC-ND-SH-A-APS-3:5000/temp/leads:latest
          resources:
            requests:
              memory: "64Mi"
              cpu: 0.5
            limits:
              memory: "512Mi"
              cpu: 0.5
          ports:
          - containerPort: 8980
          imagePullPolicy: Always```
#3

You need the set insecure registry mode

#4

Or setup HTTPS for your registry

#5
  • thanks for the input but as I mention in my original post, I have already added insecure-registries in daemon.json file under /etc/docker. The docker pull command also works btw so that should indicate that ip resolution works and registry is accessible too
#6

However you did it, it didn’t work

#7

So … do it the way that works?

#8

You probably aren’t using docker anymore

#9

It’s deprecated in Kubernetes and has already been removed in the main branch

#10

Containerd has its own config

#11

Oh ok …
> So … do it the way that works?
I didn’t catch this

#12

Okay so first, what is your CRI plugin

#13

I use k3s as kubernetes which uses containerd as the runtime

#14

Okay, then any docker config would do nothing :smile:

#15

Right good point :slightly_smiling_face:
I need to find out the config for containerd

#16 
            insecure_skip_verify = true```
#17

Seems like this overall isn’t well supported in containerd

#18

You should probably just set up TLS for the registry :stuck_out_tongue:

#19

TLS sounded tough so I thought about this route.

            insecure_skip_verify = true```
Where do I add the above text?
#20

Search for “containerd insecure registry” and you’ll find some tickets on their repo with a few examples