-
Notifications
You must be signed in to change notification settings - Fork 154
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
Cannot find buildx v0.9.1 release #190
Comments
We're having this problem with any release tag, including |
@AlanMendicutti Please post the logs of the action thanks. |
@crazy-max I got one for you if this helps:
|
Same, just started a few minutes ago. Here's the step:
And the output:
|
Sure @farvour
|
This comes from setup-buildx-action/src/buildx.ts Line 243 in 7932f62
Which relies on the GitHub API to download the binary from https://github.com/docker/buildx/releases. Best guess is GitHub has some issues. |
@crazy-max does the httpm client support 302 redirects? I did a curl of the latest and it gives me a 200, but not after giving me a 302.
Am also noticing the content type isn't JSON at all, but just plain HTML.. is GitHub not respecting an Accept header? Also appears that this project is archived/defunct? |
@farvour Looks like that might be the case. Making a request directly to the endpoint with $ curl --request GET \
--url https://api.github.com/docker/buildx/releases/latest \
--header 'Accept: application/json'
{
"message": "Not Found",
"documentation_url": "https://docs.github.com/rest"
} EDIT: I just realized I was requesting against |
@farvour I'm not sure, we are just using the GitHub Actions Toolkit: https://github.com/actions/toolkit/tree/main/packages/http-client I guess many actions could be broken atm 😟
|
Yeah even with I don't get back JSON as I would expect... I bet this is going to become a systemic issue - I wonder if GitHub is already aware but I don't know where their central status/reporting is for the API at the moment.. perhaps it'll correct itself then. |
Are there any workarounds or a central ticket people can follow where we get some feedback from github: is it temporary, or do actions need to change? |
@cep21 You can just unset |
@farvour I made some tests and using the Octokit client seems to work so far. |
#191 should solve this issue. Can someone try with |
@crazy-max fix seems to work for me https://github.com/rustielin/playground/actions/runs/4029384893/jobs/6927222954 |
Should be fixed with |
Yep, confirmed that |
@lediur https://github.com/docker/setup-buildx-action/releases/tag/v2.4.0 should fix the issue once and for all so we don't rely on this endpoint anymore. Neither the GitHub API. |
Behaviour
Running this action is returning the next message: "Cannot find buildx v0.9.1 release"
This is the step:
And this is what RUN returns:
I've been using this version since a few weeks.
Then all of the sudden this error shows up.
Does anyone knows what's going on?
Thanks in advance
The text was updated successfully, but these errors were encountered: