Problems with Insecure registry

General Discussions
1

Cluster information:

Kubernetes version: 1.30.0
Installation method: APT
Host OS: Debian 12
CNI and version: Calico, 3.25
CRI and version: Docker, 26.1.1

Hi everyone, I am deploying my first Kubernetes cluster, and i ran into some issues while deploying my first job. I use Kubeadm.
I have deployed a local docker registry on another pc, and push a simple docker image on it (my-python-app, an hello-world).

This is an insecure registry, and i believe it’s the core of the problem. My registry do not require auth.
On the cluster, i can do a docker pull after adding the docker repo as insecure in /etc/docker/daemon.json.
The problem is the job cannot pull the image even with this configuration.

The job file :

apiVersion: batch/v1
kind: Job
metadata:
  name: my-python-app
spec:
  completions: 1
  parallelism: 1
  template:
    spec:
      containers:
      - name: my-python-app
        image: 192.168.30.33:5000/my-python-app
      restartPolicy: Never

The error :

Failed to pull image "192.168.30.33:5000/my-python-app": failed to pull and unpack image "192.168.30.33:5000/my-python-app:latest": failed to resolve reference "192.168.30.33:5000/my-python-app:latest": failed to do request: Head "https://192.168.30.33:5000/v2/my-python-app/manifests/latest": http: server gave HTTP response to HTTPS client

I am a bit stuck with this error, and I cannot find anything related to this.
Thanks for your time !

3

Can you open your /etc/default/docker.json

and add an entry

{
    "insecure-registries": ["192.168.30.33:5000"]
}

Then it should work