Unable to push ai model to local docker registry

[wingertjp]

Host registry : docker run -d -p 5000:5000 --name registry registry:3

Pull model: `docker model pull ai/smollm2

Tag downloaded model: docker model tag ai/smollm2 localhost:5000/ai/smoll2

Try to push tagged ai model : docker model push localhost:5000/ai/smoll2:latest

I get thi error :

Uploaded: 0.00 MB
Failed to push model: error pushing model: Error: write to registry "localhost:5000/ai/smoll2:latest": Get "https://localhost:5000/v2/": dial tcp [::1]:5000: connect: connection refused; Get "http://localhost:5000/v2/": dial tcp [::1]:5000: connect: connection refused

PS: I can push regular docker images like busybox

[ericcurtin]

The PR highlighted something:

"The go-containerregistry library attempts HTTPS by default and lacks built-in support for insecure localhost registries."

Does

docker model push http://localhost:5000/ai/smoll2:latest

or

docker push http://localhost:5000/something/something:latest

or

docker push localhost:5000/something/something:latest

work?

[wingertjp]

Last one only, results below

• docker model push http://localhost:5000/ai/smoll2:latest

Failed to push model: pushing http://localhost:5000/ai/smoll2:latest failed with status 500 Internal Server Error: error while pushing model: new tag: invalid tag: "http:/localhost:5000/ai/smoll2:latest": repository can only contain the characters `abcdefghijklmnopqrstuvwxyz0123456789_-./`: localhost:5000/ai/smoll2

• docker push http://localhost:5000/busybox:latest

invalid reference format

• docker push localhost:5000/busybox:latest

The push refers to repository [localhost:5000/busybox]
80e840de630d: Layer already exists
latest: digest: sha256:ebd0a6156be6cdc24c4bd1ad0e0fcb938cbdd5f8b86b15d18821f280902b6380 size: 527

[ilopezluna]

Hello @wingertjp, I’ve just been working on a related PR you can see in there how local registries are being tested.

We recently added this PR, which allows you to:

• Define the default registry
• Allow insecure (HTTP) registries

However, there’s currently an issue affecting the push command. I’ll work on a fix tomorrow and will update you as soon as it’s ready.
Just wanted to keep you informed.