Insecure Registry not being set

[Taylor150]

Description

I have use colima start --edit to add my insecure registry:
docker: insecure-registries: - 192.168.172.27:6969 - repo.local:6969 - localhost:6969 - 127.0.0.1:6969

however when i do a docker login, it looks like the insecure registry is not being recognised:
docker login http://192.168.178.27:6969 Username: admin Password: Error response from daemon: Get "https://192.168.178.27:6969/v2/": http: server gave HTTP response to HTTPS client

Any suggestions?

Version

Colima Version: 0.5.6
Lima Version: 0.18.0
Qemu Version: 8.1.2

Operating System

• macOS Intel <= 12 (Monterrey)
• macOS Intel >= 13 (Ventura)
• macOS M1 <= 12 (Monterrey)
• macOS M1 >= 13 (Ventura)
• Linux

Output of colima status

colima is running using macOS Virtualization.Framework
arch: aarch64
runtime: docker
mountType: virtiofs
address:
socket: unix:///Users/laurencetaylor/.colima/default/docker.sock

Reproduction Steps

1. I have a local docker registry
2. I have set this registry in the insecure-registries within colima config
3. I have tried to docker login to the registry/docker pull
4. I receive and error which infers that the insecure registry is not recognised

Expected behaviour

Be able to login to my insecure registry

Additional context

No response

[abiosoft]

Can you kindly share the output of the following?

# display the generated docker config
colima ssh -- cat /etc/docker/daemon.json; echo

[Taylor150]

Can you kindly share the output of the following?

colima ssh -- cat /etc/docker/daemon.json; echo
{
"exec-opts": [
"native.cgroupdriver=cgroupfs"
],
"features": {
"buildkit": true
},
"host-gateway-ip": "192.168.5.2"
}

[Taylor150]

Not sure if related but i also notice these when colima is starting:
WARN[0054] unable to disable qemu x86_84 emulation: exit status 1
stat: can't stat '/proc/sys/fs/binfmt_misc/qemu-x86_64': No such file or directory

[klit79]

Me too
It was not working even if colima restart.
I had to run this
colima ssh sudo service docker restart

[amirkhonov]

colima ssh sudo systemctl daemon-reload
colima ssh sudo systemctl restart docker

worked for me.

[rodolfo-gonzalez]

in my case the .pem didn't work, had to rename it to .crt and then run update-ca-certificates

[codrutpanea]

if colima is already running and I run colima start --edit it will not apply the new insecure-registries entries. I had to first stop the colima by running colima stop and run the colima start --edit command