Merged
Conversation
Seems the [`Unexpected status from HEAD request to <url>: 400 Bad Request`](https://github.com/github/issue-metrics/actions/runs/8758107284/job/24038180863#step:5:1024) is an intermittent error in GitHub Actions and pushing to ghcr that can be solved by using moby/buildkit via docker/build-push-action#761 (comment) Going to try this with latest release of moby/buildkit to see if it fixes it Signed-off-by: jmeridth <jmeridth@gmail.com>
zkoppert
approved these changes
Apr 19, 2024
Collaborator
Author
|
This did not fix the issue. Still researching. May have to temporarily pause automated image builds until figured out. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Proposed Changes
Seems the
Unexpected status from HEAD request to <url>: 400 Bad Requestis an intermittent error in GitHub Actions and pushing to ghcr that can be solved by using moby/buildkit viadocker/build-push-action#761 (comment)
Going to try this with latest release of moby/buildkit to see if it fixes it
Readiness Checklist
Author/Contributor
make lintand fix any issues that you have introducedmake testand ensure you have test coverage for the lines you are introducingReviewer
fix,documentation,enhancement,infrastructure, orbreaking