tests/e2e: hitting docker.io/library/registry pull rate limit

[wainersm]

Describe the bug

The SEV job has failed due to hitting pull rate limit of the docker.io/library/registry:

13:27:03 TASK [Start a docker registry] *************************************************
13:27:10 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Error pulling docker.io/library/registry - code: None message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: [https://www.docker.com/increase-rate-limit"}](https://www.docker.com/increase-rate-limit%22%7D)
13:27:10 

That image is used on the e2e CI to start a locally registry: https://github.com/confidential-containers/operator/blob/main/tests/e2e/ansible/start_docker_registry.yml

Let's replace that image. Maybe push to quay.io?

[wainersm]

@ryansavino @fitzthum @UnmeshDeodhar are you aware of that problem? Anyone working to solve it?

[UnmeshDeodhar]

I can work on this @wainersm .

[wainersm]

Cool, thanks @UnmeshDeodhar

[ryansavino]

@wainersm we were discussing a bit in slack.

operator/tests/e2e/ansible/start_docker_registry.yml

Line 28 in a0fbbf4

image: docker.io/library/registry:latest

Can we host a registry image from quay?

[wainersm]

Hi @ryansavino ,

@wainersm we were discussing a bit in slack.

operator/tests/e2e/ansible/start_docker_registry.yml

Line 28 in a0fbbf4

image: docker.io/library/registry:latest

Can we host a registry image from quay?

Yesterday I spent some time looking for images that could replace docker.io/library/registry:latest and I found none. So if there isn't any legal impediment (I don't think there is) then we could have a copy of that image on quay.io, yes.