We migrated dev-images from the Debian Stretch base to Buster under T273100. Definitions for the stretch images remain in the repo. We should probably remove these.
Open question: Can / should these be deleted from the Docker registry?
We migrated dev-images from the Debian Stretch base to Buster under T273100. Definitions for the stretch images remain in the repo. We should probably remove these.
Open question: Can / should these be deleted from the Docker registry?
Title | Reference | Author | Source Branch | Dest Branch | |
---|---|---|---|---|---|
remove stretch-* definitions | repos/releng/dev-images!2 | brennen | brennen/remove-stretch-definitions | main |
Open question: Can / should these be deleted from the Docker registry?
My understanding is that they'll stop being listed now (because we dropped them from git), but won't be removed from the registry (so existing things yet to transition won't suddenly break).
My understanding is that they'll stop being listed now (because we dropped them from git)
Hmm - this is possible, but if so I'm not sure what the mechanism is.
There's some magic in the puppet-managed code for the docker registry; it was done to stop listing jessie- and stretch-based images from the releng/ namespace (not dev/), but I think it was written to be general?
I see some stuff in modules/profile/files/docker/reporter/releng_rules.ini for docker-report. I'm not, however, entirely sure what docker-report does.
It seems like, in general, removing images is discouraged.
Optimistically calling this one resolved.