Use galaxy-ng as a container hub

Hi,
I want to use galaxy-ng as a “internal container hub” like dockerhub. But I’ve a problem when I attack it with podman. It returns me the following error:

Error: authenticating creds for "10.160.45.4:30000": pinging container registry 10.160.57.12:30000: Get "https://10.160.45.4:30000/v2/": http: server gave HTTP response to HTTPS client

Anyone, can tell me how to solve it?

Thanks in advance!

You could either reconfigure your nginx to listen on https and proxy to the http endpoint,
or you could use podman with --tls-verify=false, which will allow it to understand http.

1 Like