Fully qualified is indeed the way to go. Unfortunately a lot of tutorials manifests and other materials have short names, and changing the default registry just opens up a load of typo squatting attacks.

That's a very good argument, but people have down used to dropping the domain prefix because it's always been optional.

Giving people the option to configure a default repository via the daemon.json would alleviate that issue, but I'm not sure if that's really enough to fork.

They’ve been betting it’s not for about ten years.

With these changes, I can imagine “intro to docker” tutorials breaking.

I suspect that’ll be enough to let a fork/competitor gain significant market share.

hm.. switch to fork just to avoid trivial, mechanical, 10-character change in docs and scripts? (image/name -> my-repo.com/image/name)

I doubt it.

The web is absolutely littered with docker tutorials and a huge proportion of them (not operated or maintained by docker themselves) would no longer be valid, I'm sure.

Oh great, so now it's a hidden default that might be different system-to-system. Disjoint from the actual deployment config. Please, dear god, no. I'm sorry, this is a bad idea.

It's just not that hard to go fully qualified.

If you specify the fully qualified image location then it's irrelevant. It's only when you decide to use short hand that it comes into concern

I agree it's the better proposal, but it does slightly break the "drop-in"-ness of Podman.

When using Podman as an alias for Docker, it does automatically resolve from Dockerhub when not specified. This is configurable, though.

That said, they also maintain a list of aliases for a bunch of container images. https://github.com/containers/shortnames . My distro's podman package then drops in that file into /etc/containers/registries.conf.d/ via one of the package's dependencies.