You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have docker registry installed let say on 5000 (by default). Reverse proxy with nginx configured to listen 5500, basic authorization is on, and ssl is on as well. (Like it is described in many of blog posts). All things work well.
I do docker login https://host_name:5500 it does work well also, but if as a next step I try to do docker push host_name:5500/ubuntu:latest it seems like docker tries to connect my registry on default for ssl TCP port 443... I get something like that Failed to upload metadata: Put https://host_name/v1/images/.../json: dial tcp XXX.XXX.X.X:443: connection timed out
Why the docker don't use the port it is logged in? Maybe I missed something? Is there any workaround? Help me please.
The text was updated successfully, but these errors were encountered:
Hi,
I have docker registry installed let say on 5000 (by default). Reverse proxy with nginx configured to listen 5500, basic authorization is on, and ssl is on as well. (Like it is described in many of blog posts). All things work well.
I do
docker login https://host_name:5500
it does work well also, but if as a next step I try to dodocker push host_name:5500/ubuntu:latest
it seems like docker tries to connect my registry on default for ssl TCP port 443... I get something like thatFailed to upload metadata: Put https://host_name/v1/images/.../json: dial tcp XXX.XXX.X.X:443: connection timed out
Why the docker don't use the port it is logged in? Maybe I missed something? Is there any workaround? Help me please.
The text was updated successfully, but these errors were encountered: