add explicit registry to docker image names

[saimonn]

closes #7495

Some container engines (hello podman 👋 ) don't use registry.hub.docker.com by default and won't be able to load redis or pgvecto-rs images from the composition.

This pull request explicitly add the image name prefix needed to fix that.

[jbtrystram]

Nice ! Thanks for giving podman some love :)

[wutr]

I've been using docker.io (instead of registry.hub.docker.com/library/) since migrating to podman a year ago. I think docker.com does some DNS magic to get to the correct server.

docker.io seems a bit more readable. Is there anything against using it instead?

edit: Unless it is podman that does the magic to get to registry.hub.docker.com/library when it receives docker.io.

edit2: docker.io has A records that directly point to the same AWS IPs as hub.docker.com (the latter via a few CNAME records). I can't find any documentation that favours one over the other or even clarifies things. Maybe I'm looking in the wrong places. Docker's own documentation doesn't seem to mention it. And of course Docker only searches its own registry so they have no need to explain.

docker.io/library is for "official" images, updated here by pull requests: https://github.com/docker-library/official-images

docker.io/repo (repo being the name registered by the repository's owner) is for images published directly by the repository's maintainer.

(docker.io and hub.docker.com can be used interchangeably)

[tleydxdy]

it appears that registry.hub.docker.com is blocked by GFW in china while docker.io is not (very strange yes). with this merge I was unable to pull new images on my chinese server. Of course the blocking action can change anytime and I wouldn't expect immich devs to have to deal with it. but in the mean time can we change the host to use docker.io? I've changed it locally, and hopefully others running into the same issue can find this comment.