-
Notifications
You must be signed in to change notification settings - Fork 862
Description
We should avoid depending on external resources as much as possible for reliable CI testing.
There are two problems with that.
First, the image on the remote could change or be removed at any time because we do not own it which would break the tests. IMO we should only ever use images under the quay.io/libpod namespace that we control.
Second, pulling from the internet is always prone to many flakes, the image should be cached in a local registry to avoid failures during registry outages. We have a working cache registry setup in cirrus but we do not cache the registry.fedoraproject.org/fedora-minimal:latest image there.
If that specific image is needed we should mirror it once into our quay.io namespace and then cache it from there in the automation setup. However I think it would be easier to use one of the existing images that we already have cached, see https://github.com/containers/automation_images/blob/f972e81d74d56699839fd6d5b3bfd0cf1edb80ef/cache_images/local-cache-registry#L56-L97