roadmap [Docker Hub] Add the ability to transfer a repository between users/organizations

Tell us about your request Add the ability to transfer a repository between users/organizations.

Which service(s) is this request for? Docker Hub

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? "Similar to how GitHub supports repository transfers, I'd like to be able to move repositories on Docker Hub without disrupting users. In particular, I'd like to transfer mdillon/postgis to appropriate/postgis. I would expect this to put in place some sort of "redirect", similar to what GitHub does, to allow users to continue pulling mdillon/postgis." - per hub-feedback/issues/328

This is sort of related to the ability to rename users and organizations in #11 and #12 since a similar redirect functionality would be needed there.

Are you currently working around the issue? NA

Additional context https://github.com/docker/hub-feedback/issues/328

Mar 25 '20 23:03 pkennedyr

Keep in mind that GitHub has a lot of restrictions for this (due to all of the things related to GitHub repositories). I think it could be easier in that respect (naive) but we would need to think hard about redirects. GitHub has the condition on redirects that if after renaming, transferring, or otherwise deleting the repository, if a new repository with the same name is created under the same user/organization, then the redirects stop working.

Something I've always wanted in Github is the ability to lock a namespace but continue to redirects to wherever it was moved. I'm not sure if we want something like that or if we want to have similar conditions for when redirects no longer work.

Mar 27 '20 15:03 ingshtrom

I literally just ran into this issue. I have a project that was started as a personal project which I just migrated under a much larger organization. I'd like to transition https://hub.docker.com/r/herbrandson/k8dash to https://hub.docker.com/r/indeedoss/k8dash, but don't want to loose the ~1M downloads. More importantly, I'd like to have people who are pointing at the original package to continue to get updates w/o having to publish to 2 different repos going forward.

May 08 '20 15:05 herbrandson

I have the same problem with my repo https://hub.docker.com/r/robertslando/zwave2mqtt I would like to move to dockerhub openzwave org but I would loose all stats and also users will have to change the tag. I think this feature is a must have for DockerHub

Jul 23 '20 08:07 robertsLando

Same issue here for https://hub.docker.com/repository/docker/tvial/docker-mailserver with 40M+ pulls.

I'd like to transfer it to a github + docker organization keeping history/stats (it's now clearly more a community project than a personal project and should not be listed anymore under my personal name).

It's possible for Github, not for Docker.

Aug 24 '20 16:08 tomav

Same here. I need to move several repositories. It worked like a charm on github.

Sep 02 '20 15:09 gregory-fonkatz

Same here, i want to transfer a repository to our organization, but we don't want to lose the downloads number.

Dec 26 '20 09:12 ruibaby

Transfer the repository is not a problem. The problems are 1. Transfer statistics. 2 Transfer the License. When you do it in GitHub your License file is moved together with the repository. Docker image in the DockerHub has only an indirect reference to the License. If some corporate developers already use your image the corporate IP advocate will stop delivery of their software instantly. This is a big difference from his point of view in using an image from /pennendyr/ namespace to /pennendyr-Company/ namespace. Who is the license issuer?