You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
GHES: parameter token or opts.auth is required #194
@crazy-max & co. I see that you are doing lots of commits currently to GHES items as well. However, like newest instructions says that use tag v3. However, no such tag exists in this repository? At least I did not like the way the backwards compatibility is handled here. All of our nightly builds failed and all pipelines are currently broken which uses this action.
If I understand this correctly, everything were working without token until #191 & #192 and now everyone should start making PATs in github.com if using GHES? Well...
changed the title [-]setup-buildx-action broken in GHES: parameter token or opts.auth is required[/-][+]GHES: parameter token or opts.auth is required[/+]on Jan 28, 2023
It should be docker/setup-buildx-action@v2 in the instructions, will fix this.
If I understand this correctly, everything were working without token until #191 & #192 and now everyone should start making PATs in github.com if using GHES? Well...
We got an issue yesterday #190 with a GitHub API endpoint we were using to check releases on buildx repository. We have to switch to the official Octokit client.
Looking at your workflow it should use the current Buildx version available on your runner. I will take a look.
why we should have buildx located in runner beforehand? It does not support downloading buildx anymore? We are hosting our github action runners in kubernetes. The runners will download the packages that they need, and now it looks like it does not work anymore.
If not found then we need to check latest stable on Buildx repo which uses the GitHub API. Previously we could make unauth call to a specific endpoint https://github.com/docker/buildx/releases/latest but it broke yesterday without notice 😣
I will check if we can just host ourselves the latest version on buildx repo so we don't need any API calls.
In the meantime you can have this step before the docker/setup-buildx-action step:
Activity
zetaab commentedon Jan 28, 2023
@crazy-max & co. I see that you are doing lots of commits currently to GHES items as well. However, like newest instructions says that use tag v3. However, no such tag exists in this repository? At least I did not like the way the backwards compatibility is handled here. All of our nightly builds failed and all pipelines are currently broken which uses this action.
If I understand this correctly, everything were working without token until #191 & #192 and now everyone should start making PATs in github.com if using GHES? Well...
[-]setup-buildx-action broken in GHES: parameter token or opts.auth is required[/-][+]GHES: parameter token or opts.auth is required[/+]crazy-max commentedon Jan 28, 2023
@zetaab
It should be
docker/setup-buildx-action@v2in the instructions, will fix this.We got an issue yesterday #190 with a GitHub API endpoint we were using to check releases on buildx repository. We have to switch to the official Octokit client.
Looking at your workflow it should use the current Buildx version available on your runner. I will take a look.
zetaab commentedon Jan 28, 2023
why we should have buildx located in runner beforehand? It does not support downloading buildx anymore? We are hosting our github action runners in kubernetes. The runners will download the packages that they need, and now it looks like it does not work anymore.

crazy-max commentedon Jan 28, 2023
https://github.com/docker/setup-buildx-action#using-on-ghes
On public runners Buildx is pre-installed: https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md
If not found then we need to check latest stable on Buildx repo which uses the GitHub API. Previously we could make unauth call to a specific endpoint
https://github.com/docker/buildx/releases/latestbut it broke yesterday without notice 😣I will check if we can just host ourselves the latest version on buildx repo so we don't need any API calls.
In the meantime you can have this step before the
docker/setup-buildx-actionstep:zetaab commentedon Jan 28, 2023
yeah it seems to work if we cache buildx to the runner image
crazy-max commentedon Jan 28, 2023
@zetaab #196 should help for your case. You can try with
crazy-max/docker-setup-buildx-action@dl-no-token.