You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People may still accidentally use the drud org on hub.docker.com (https://hub.docker.com/u/drud). It's been a year since we left it behind, but there may be still people out there using versions of ddev that use those images.
Describe your solution
I propose making the images in the entire org private. It's better than deleting them outright. Then in another year we can just delete that org or delete everything in it.
Describe alternatives
Let things just move along like they are. The next time Docker Open Source wants an update they'll want all the descriptions done and all though, and we won't want to do it, so this will come to an end before too long anyway.
Additional context
No response
The text was updated successfully, but these errors were encountered:
I propose making the images in the entire org private. It's better than deleting them outright. Then in another year we can just delete that org or delete everything in it.
This sounds like the safest strategy.
I wonder, does Docker hub have an "archive" option like GitHub?
Is there an existing issue for this?
Is your feature request related to a problem?
People may still accidentally use the
drud
org on hub.docker.com (https://hub.docker.com/u/drud). It's been a year since we left it behind, but there may be still people out there using versions of ddev that use those images.Describe your solution
I propose making the images in the entire org private. It's better than deleting them outright. Then in another year we can just delete that org or delete everything in it.
Describe alternatives
Let things just move along like they are. The next time Docker Open Source wants an update they'll want all the descriptions done and all though, and we won't want to do it, so this will come to an end before too long anyway.
Additional context
No response
The text was updated successfully, but these errors were encountered: