docker run registry?

[znd4]

I'd like to be able to run an image registry with TLS at an address that's accessible from my host (MacOS) and inside orbstack containers (for kubernetes). I'm trying

docker run --rm --name registry -l dev.orbstack.https-port=5000 registry

but get this when I try to pull from it:

>  docker pull registry.orb.local/foo
Using default tag: latest
Error response from daemon: Get "https://registry.orb.local/v2/": http: server gave HTTP response to HTTPS client

my guess is that orbstack mistakenly thinks that registry is trying to manage TLS, but it isn't. Is there a way to force orbstack to handle TLS?

other stuff I've tried

docker run --rm --name registry -e REGISTRY_HTTP_ADDR=0.0.0.0:443 registry

same error (server gave HTTP response to HTTPS client)

docker run --rm --name registry registry
# in another shell
docker pull registry.orb.local:5000/foo

same "HTTP response to HTTPS client" error

Everything else gives ...dial tcp {IP}: connect: connection refused

[kdrag0n]

my guess is that orbstack mistakenly thinks that registry is trying to manage TLS

That's what dev.orbstack.https-port means. Use dev.orbstack.http-port insetad.

[znd4]

hmm when I use -l dev.orbstack.http-port=5000, I get the same client behavior as a raw docker run --rm --name registry registry:

>  docker pull registry.orb.local/foo
Using default tag: latest
Error response from daemon: Get "https://registry.orb.local/v2/": dial tcp 192.168.215.2:443: connect: connection refused

>  docker pull registry.orb.local:5000/foo
Using default tag: latest
Error response from daemon: Get "https://registry.orb.local:5000/v2/": http: server gave HTTP response to HTTPS client

I brew installed orbstack a few days ago. do i need to build from source for that label to work?

[znd4]

edit: nvm, I think the docker client just doesn't try to distinguish between failed networking connections and valid 404s.