-
Notifications
You must be signed in to change notification settings - Fork 145
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
GHES: parameter token or opts.auth is required #194
Comments
@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... |
It should be
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. |
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 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 - name: Download buildx
run: |
mkdir -p ~/.docker/cli-plugins
wget https://github.com/docker/buildx/releases/download/v0.10.1/buildx-v0.10.1.linux-amd64 -O ~/.docker/cli-plugins/docker-buildx
chmod +x ~/.docker/cli-plugins/docker-buildx |
yeah it seems to work if we cache buildx to the runner image |
Behaviour
Steps to reproduce this issue
Expected behaviour
I expect that it should work like before
Actual behaviour
Configuration
Logs
The text was updated successfully, but these errors were encountered: