Comment Comment by horsawlarway Personally - I don't really see this one making sense.There's already a widely available way to specify exactly which repo you'd prefer in the docker client...`docker pull [repo]/[image]:[tag]`And that address format works across basically all of the tooling.Changing the defaults doesn't actually make sense, because there's no guarantee that repo1/secure_image === repo2/secure_image.Seems like a HUGE security issue to default named public images to a repo where the images may not be provided by the same owner. parent horsawlarway 1 year ago
There's already a widely available way to specify exactly which repo you'd prefer in the docker client...
`docker pull [repo]/[image]:[tag]`
And that address format works across basically all of the tooling.
Changing the defaults doesn't actually make sense, because there's no guarantee that repo1/secure_image === repo2/secure_image.
Seems like a HUGE security issue to default named public images to a repo where the images may not be provided by the same owner.