Fix - Quay Storage Directory

[sveno1990]

Currently if you run the installer with a user that does not have UID = 1000 and has a umask that is not 002 (e.g. 027) and quayStorage pointing to a (not yet) existing dir. The container wil not have permissions to write files in the directory. The commit should fix this.

The describe situation results in bad gateway 502 errors in when pushing to the registry. In the quay-app this results in various permission denied errors in the logs.

[harishsurf]

good catch, thank you for your contribution!

[bcaton85]

/cherry-pick mirror-registry-2.0-rhel-8

[openshift-cherrypick-robot]

@bcaton85: new pull request could not be created: failed to create pull request against quay/mirror-registry#mirror-registry-2.0-rhel-8 from head openshift-cherrypick-robot:cherry-pick-175-to-mirror-registry-2.0-rhel-8: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between quay:mirror-registry-2.0-rhel-8 and openshift-cherrypick-robot:cherry-pick-175-to-mirror-registry-2.0-rhel-8"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to this:

/cherry-pick mirror-registry-2.0-rhel-8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.