spin can not login docker private registry while docker login success about spin

[xiaocode]

@rajatjindal @vdice Thanks to both of you.It works now!

[rajatjindal]

the same flag --insecure works with spin up as well. (i just verified it)

spin up -f localhost:5000/myapp:latest --insecure

Serving http://127.0.0.1:3000
Available Routes:
  http-ex: http://127.0.0.1:3000 (wildcard)
Handling request to Some(HeaderValue { inner: String("http://127.0.0.1:3000/") })

[xiaocode]

After I clone the latest spin repo and build, I got different response:

Error: cannot log in to the registry

Caused by:
      cannot authenticate as admin to registry docker.registry.local:5000: http transport error: error sending request for url (https://docker.registry.local:5000/v2/): error trying to connect: error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:354:

Spin version:
spin 2.7.0-pre0 (7833e71 2024-06-28)

[vdice]

Hello @xiaocode,

The failures you are seeing are due to Spin's login client attempting to ensure a secure https connection with the local private registries which I assume are running unsecured (eg via http). The spin registry login command doesn't yet support insecure/http registries (see #1211).

However, for any local registry running via http, you can proceed in using the other spin registry push/pull commands without needing to authenticate. You just need to also supply the --insecure/-k flag. For example: spin registry push docker.registry.local:5000/myapp:latest --insecure. Can you give that a try and let us know if you are still experiencing issues?

[xiaocode]

@vdice Thank you for your anwser.
I have tried to use spin registry push docker.registry.local:5000/myapp:latest --insecure and success, but I when I try to use spin up -f with and pass the registry reference, It shows that need the docker registry must use https to retrieve images.
I just want to use spin with local docker registry so that I can run this totally without Internet.