Make the postgis docker images available from cr.postgis.net

[strk]

It would be nice to make the PostGIS docker images available from a postgis.net domain, so users are not required to change their "fetch url" when/if our images move from an hoster to another, and also to unify them (at the moment some are on OSGeo docker registry, some on $wontname proprietary hoster's).

See ​https://wiki.osgeo.org/wiki/SAC:Repo#Docker for the OSGeo registry

[strk]

I've done some experiments with HTTP redirects under Apache but are currently failing and I run out of time. CI showing the failure is here: ​https://github.com/postgis/postgis/pull/722

[robe]

strk I'm not following what you are doing in that pull request. You are changing the push task which we never use. The push task is at - ​https://github.com/postgis/postgis-build-env

But at anyrate, I think we don't need vanity urls for push tasks. We only need vanity for pull, the ones the ci bots and users will be using. Push we probably want to control where we push to.

[robe]

I'm going to set docker.postgis.net to be on osgeo8. I was trying to set aside osgeo8, for project specific needs that may be somewhat risque. Not saying this is risque, but just a server, that if I need to restart, wouldn't cause too much interruption.

Now the question is how do I setup this redirect stuff. Is it literally just a redirect.

[robe]

actually dbb got me thinking. Do we even want to call this docker.postgis.net as docker is more the name of a company rather than a technology we want to promote.

e.g. podman and other tools can use these images and eventually we might want to expose non-compatible docker images.

If you note, githubs container registry doesn't even have docker in the name. It's ghcr.io.

So perhaps something like cr.postgis.net (for container registry) might be a more suitable name. And it's shorter to type

[lnicola]

​https://httptoolkit.com/blog/docker-image-registry-facade/ has a nice discussion of proxying docker HTTP requests. But I'm not sure it works with multiple back-end repositories, given the authentication step that happens before requesting a manifest.

Is it important that the user/production and dev/ci images are on different registries?

[robe]

Replying to lnicola:

​https://httptoolkit.com/blog/docker-image-registry-facade/ has a nice discussion of proxying docker HTTP requests. But I'm not sure it works with multiple back-end repositories, given the authentication step that happens before requesting a manifest.

Is it important that the user/production and dev/ci images are on different registries?

We'd want them accessible for pull on the same registry I think, but where they are actually stored we don't care so much.