Docker registry HTTP / HTTPS mismatch
Open, NormalPublic
Actions

Assigned To

None

Authored By

	dereckson
	Mar 9 2023, 01:46

Description

After a docker pull from localhost:5000 local registry on docker-002:

Mar 9 01:43:24 docker-002 dockerd[2844209]: time="2023-03-09T01:43:24.930882796Z" level=warning msg="Error getting v2 registry: Get \"https://localhost:5000/v2/\": http: server gave HTTP response to HTTPS client"
Mar 9 01:43:24 docker-002 dockerd[2844209]: time="2023-03-09T01:43:24.931528815Z" level=info msg="Attempting next endpoint for pull after error: Get \"https://localhost:5000/v2/\": http: server gave HTTP response to HTTPS client"

If we use registry.nasqueron.org on docker-002 too, it works like a charm:

$ docker pull registry.nasqueron.org/postgres-sentry:D2867
D2867: Pulling from postgres-sentry
Digest: sha256:4a06dd82d2583b007c12ab5b965eb48288e16891f9d69f13a62e6555efb12869
Status: Downloaded newer image for registry.nasqueron.org/postgres-sentry:D2867
registry.nasqueron.org/postgres-sentry:D2867

Should we update rINFRAWWW documentation?

File to update: https://devcentral.nasqueron.org/source/infra-www/browse/main/src/partials/docker-registry/docker-registry-help.html