docker push to new repo creates it as private

[Daniel Hiller]

Hey,

we recently created a new account for automated updates of our image repositories. Now the first time this account created a repo via docker push it was created as a private repository. I don't understand why this could happen as according to the plan the account is not eligible to create private repositories.

I've searched for a user setting that has defaults but couldn't find any. Can someone please give me some pointers? Or is this a bug? Then where can I file it?

Thanks in advance!

Daniel Hiller

[thomasmckay]

It is intentional that a push to a non-existent repository creates it as private. The thinking is that it would be unfortunate if a push leaked private containers unintentionally (ie. it is intended to help users). Visiting the UI, the repo may be changed to public.

For running quay on-premise (not quay.io), there is work underway[1] to make that configurable.

[1] https://issues.redhat.com/browse/PROJQUAY-1929