Marcel Singer

In my case the issue seems to be caused by building two images sequentially without using the `--cleanup` flag (we originally omitted it as a workaround for #1568). The first...

@rajivml We observed similar behavior, that was caused by an admission controller (in our case kyverno) interfering with an update request by the job-controller.

> I ran a `docker pull .azurecr.io/docker.io/infracost/infracost:ci-0.10` from local machine this morning to test the caching rule (the rule simply caches everything from `docker.io/*`. > > The image got pulled...

I've received the following response by a Microsoft support technician. > It is an issue we are aware of, and due to the aforementioned recent rate limit changes the bug...

@microsoft-github-policy-service agree company="lise GmbH"