-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Action is encountering internal issue and sits in a retry loop(?), chews up action minutes #498
Comments
Wanted to see if the workflow was at fault so changed it to be all sequential and received a new error...
Is this some sort of upstream issue with IMO, this action has an issue where it's not correctly exiting or retrying after hitting these errors though... however more importantly I'd like to know whats going wrong and if/how I can resolve it on my end 😄 |
This has been happening to me for days now:
This seems to have been an ongoing issue for a while but I haven't tracked down which version of BuildKit is at play here yet: docker/buildx#367 |
Possibly related: containerd/containerd#6242 Appears that the issue is indeed upstream and (unless I'm corrected), unrelated to this action |
Yes that's it, tracked in docker/buildx#834 and PR opened on BuildKit repo: moby/buildkit#2461. In the meantime use the solution from docker/buildx#834 (comment). |
Cool, thanks @crazy-max Puts things a bit more at ease having it confirmed to be getting handled upstream :) |
docker/build-push-action#498 (comment) docker/buildx#834 moby/buildkit#2461 Looks like a fix is merged into buildkit, but we have to wait for a new release to get the fix.
Seems like I encountered this in docker/buildx#1728, not sure if @South-Paw you have confirmation of the fix upstream? |
To this day, I'm unsure if it's been fixed upstream 😂 (more because I haven't revisited or kept up with the issues). I still have @crazy-max's solution in place to avoid it |
This was working fine 7 days ago and there have been no changes to our workflows however now this action is having some issue occur internally which results in it sitting in what appears to be a retry loop or its hung. This has cost us a few hours total of paid action minutes.
Behaviour
Steps to reproduce this issue
Expected behavior
This was originally (as of the 7th of Nov) working fine - the workflow would complete as expected and containers A and B would be published to the GHCR, both tagged
dev
andtest
correctly.Actual behavior
Workflow runs today are now getting stuck in what appears to be a retry loop(?) and only one of the two parallel jobs will pass, the other gets stuck in a loop(?) and need to be cancelled.
When the jobs are cancelled, the job log has the following:
Given the timestamps, it's clearly not retrying in on second ... or at all for that matter.
Run examples:
Configuration
YAML workflow file
The text was updated successfully, but these errors were encountered: