Comment 10 for bug 1999749

Thank you Takashi for digging deep into that, I think you are correct. I tried the buildah login on the box.
```
[zuul@node-0003383040 ~]$ buildah login -v -u ** quay.rdoproject.org
Password:
Used: /run/user/1000/containers/auth.json
Login Succeeded!
[zuul@node-0003383040 ~]$ sudo buildah login -v -u ** quay.rdoproject.org
Password:
Used: /run/containers/0/auth.json
Login Succeeded!
[zuul@node-0003383040 ~]$
```
In periodic container build job, we are running buildah using sudo, so, we need to point
REGISTRY_AUTH_FILE to /run/containers/0/auth.json.

```
[zuul@node-0003383040 ~]$ export REGISTRY_AUTH_FILE=/run/containers/0/auth.json
[zuul@node-0003383040 ~]$ sudo buildah login -v -u tripleo quay.rdoproject.org
Password:
[zuul@node-0003383040 ~]$ sudo -E buildah login -v quay.rdoproject.org
Authenticating with existing credentials for quay.rdoproject.org
Existing credentials are valid. Already logged in to quay.rdoproject.org
[zuul@node-0003383040 ~]$ sudo buildah login -v quay.rdoproject.org
Authenticating with existing credentials for quay.rdoproject.org
Existing credentials are valid. Already logged in to quay.rdoproject.org
```
I think we can fix it in config side by passing this env var and try it out.