Open jixawang opened 1 month ago
I see that IP-address is configured as an insecure registry, in which case the daemon may be falling back to using non-TLS connections if connecting through TLS fails;
Insecure Registries:
10.157.161.133
10.158.46.38
cncappdlv5053
dockerproxy.com
hubproxy.docker.internal:5555
10.157.109.75
10.157.112.144
cncappplv5388
127.0.0.0/8
Description
Hello,
I have already config "insecure-registries" in my windows docker engine.
When i try to "docker login https://10.157.161.133 -u admin -p xxxx
it will auto transfer to http
Error response from daemon: login attempt to http://10.157.161.133/v2/ failed with status: 403 Forbidden
![图片](https://github.com/user-attachments/assets/a87e270d-5483-48a9-871a-2f3cdab8e891)
Reproduce
docker login harbor
Expected behavior
No response
docker version
docker info
Additional Info
No response