- In a hostRule for matchHost: https://quay.io/v2/ the user and password of a quay robot account should be used.
- In a different hostRule for matchHost: https://quay.io/api/v1/ the OAuth token of an []organisation application](https://docs.quay.io/api/#generating-a-token-for-internal-application-use) should be used as you mention.
quay.io configuration
{
"hostRules": [
{
"hostType": "docker",
"matchHost": "https://quay.io/v2/",
"username": "usr",
"password": "apitoken"
},
{
"hostType": "docker",
"matchHost": "https://quay.io/api/v1/",
"token": "apitoken"
}
]
}Create a repository using this template →
$ curl -sv https://quay.company.com/v2/auth?service=quay.company.com&scope=repository:repo/org:pull
$ skopeo list-tags --no-creds docker://quay.io/jetstack/cert-manager-controller
$ skopeo list-tags --no-creds docker://quay.io/coreos/kube-state-metrics
$ skopeo list-tags --no-creds docker://quay.io/helmpack/chart-testing
$ skopeo list-tags --no-creds docker://quay.io/argoproj/argocd
- Quay authentication issue (issue-10188)
- Self-Hosted quay enterprise support(Issue-13709)
- Docker quay.io label fetching error (issue-4626)
