@raph @bagder Nothing is stopping projects from moving,...

@raph @bagder Nothing is stopping projects from moving, but container registries exist in large part to allow other projects to automatically get images from them. Communicating to those projects that the image has moved is very difficult, and there's no evidence that the DockerHub will take the necessary steps to make things easier. I also believe that DockerHub is the default registry used by Docker, exacerbating the problem.

Like 16 Mar 2023 at 1:05 | Wall-to-wall | Open on social.coop

4 comments

Shauna GM

@raph @bagder Basically: people (and automated scripts) are going to be looking on DockerHub for images that are no longer there. In the best case scenario, this will break a ton of scripts and be a huge hassle for a long time as people slowly update where they're getting images from. In the worst case scenario, you'll have malicious namespace squatting in the deleted accounts. (DockerHub's said they'll keep namespaces safe/reserved but there's not a lot of trust right now for obvious reasons.)

16 Mar 2023 at 1:07 | Open on social.coop

Raph

@shauna @bagder got it, thank you for explaining 🙏 so newer projects, that don't have humans or scripts looking at a particular registry yet, could move to another container registry, and all would be well? There are no particular down sides *not* being on DockerHub?

16 Mar 2023 at 1:31 | Open on social.coop

Shauna GM

@raph @bagder That's my understanding. I don't use Docker/DockerHub much though, and certainly don't have any major projects that are getting hundreds of thousands of public downloads, so take my explanations with a pinch of salt. :)

16 Mar 2023 at 1:59 | Open on social.coop

Raph

@shauna @bagder Sounds good, this is already helpful. We're about to release two web apps that use Docker so this is a timely conversation 😅

16 Mar 2023 at 3:01 | Open on social.coop