GHA failed to solve: maximum timeout reached

[lucacome]

I've seen this error a few times lately:

#19 exporting cache
#19 preparing build cache for export done
#19 ERROR: maximum timeout reached
------
 > exporting cache:
------
error: failed to solve: maximum timeout reached
Error: buildx failed with: error: failed to solve: maximum timeout reached

Would it make sense to not have the build fail if the cache can't be exported?

[ghostwriter]

If I'm not mistaken, I believe GitHub Action Cache is returning Error 429 when importing/exporting cache, which causes Buildkit to Exponentially backoff and the build process to timeout.

[lucacome]

I'd like to bump this issue as it seems like the number of timeout issues has increased.

Almost same output as before:

#20 preparing build cache for export 307.8s done
#20 ERROR: maximum timeout reached
------
 > exporting to GitHub cache:
------
ERROR: failed to solve: maximum timeout reached
Error: buildx failed with: ERROR: failed to solve: maximum timeout reached

I don't know if it's a coincidence, but it seems to happen more if multiple PRs run the workflow at the same time.

[mnapoli]

I am experiencing this problem randomly as well.

[lucacome]

I'd really like to at least have the option to make it fail "silently". A lot of my builds are failing because of this and I'd prefer to lose the cache and finish the pipeline rather than failing and having to restart the entire build process.

[dotansimha]

Seems like this has become relevant again. Today most of the attempts to push a Docker image failed with maximum timeout reached.

Update (Nov 26): Still having the same issues. We are building ~10 images and it seems like it timeouts ~20% of the times.

[danielsantiago]

In May the ignore-error=true option was added to ignore errors when remote cache-exports fail. #3430