action #67855
Updated by okurz over 4 years ago
## Observation I have seen an observation similar to the following often in past weeks, latest example https://app.circleci.com/pipelines/github/os-autoinst/openQA/3231/workflows/17a0a4f7-8fe9-47e3-a50d-191a87c75cc8/jobs/30830/steps: ``` Starting container registry.opensuse.org/devel/openqa/ci/containers/base:latest image cache not found on this host, downloading registry.opensuse.org/devel/openqa/ci/containers/base:latest latest: Pulling from devel/openqa/ci/containers/base 81e5221d78cb: Pulling fs layer 3e86cb3bb3f5: Pulling fs layer 81e5221d78cb: Verifying Checksum 81e5221d78cb: Download complete 81e5221d78cb: Pull complete error starting container registry.opensuse.org/devel/openqa/ci/containers/base:latest: Error: No such image: registry.opensuse.org/devel/openqa/ci/containers/base:latest Error: No such image: registry.opensuse.org/devel/openqa/ci/containers/base:latest ``` so while it looks like the layers of the container are downloaded still after 10m there is the error `error starting container registry.opensuse.org/devel/openqa/ci/containers/base:latest: Error: No such image: registry.opensuse.org/devel/openqa/ci/containers/base:latest`. Probably the base 81e5221d78cb is present in cache but 3e86cb3bb3f5 fails to load. Locally I can see that this blob has 492 MiB so maybe it's just a bit big. ## Acceptance criteria * **AC1:** Multiple circleci jobs succeed to create the container based environment ## Suggestions * ~~Maybe Maybe it can already help if we use `--no-recommends` within the package installs within Dockerfile to reduce the size of layers~~ -> nope, see #67855#note-1 * Add a retry within the circleci jobs or on the level of how circleci jobs are triggered layers