-
Notifications
You must be signed in to change notification settings - Fork 921
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
Fix buildx
installation
#2952
Fix buildx
installation
#2952
Conversation
cc: @TingluoHuang. If we could get a patch release for |
This seems to be causing an issue for some container actions. Example when using hadolint-action in a workflow.
|
As far I as know, this hasn't been released yet. So I'm not sure if this is what's causing your problem. |
Fair enough. The latest image for 2.311.0 was updated 1 day ago, and I assumed this part of that update |
@ajschmidt8 was curious if this was related...We tried to run runner version 2.310.2 from current 2.209.0 and something has changed to where what was working fine now is failing and seems to be related possibly to Docker. Was wondering if this error indicates related to this issue or not please? |
This PR hasn't been included in any runner release yet. I would recommend reviewing the release changelogs to identify any changes that may have affected your workflows. Disclaimer, I don't work for GitHub and therefore don't provide any support for these changes. |
Thank you and yes understand. Was seeing if you may have an idea of what may be happening. Thank you. |
For anyone facing this issue
This will tell it to go to a different folder @ajschmidt8 maybe we should set it in a folder that we know is not read-only by default? |
This PR is a continuation of #2901.
I hadn't tested that change locally and didn't realize the Dockerfile did a multi-stage build.
This PR fixes the
buildx
installation to ensure that the binary is copied to the final stage.I tested these changes locally to confirm that it works as expected.