-
Notifications
You must be signed in to change notification settings - Fork 533
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
Bumped docker/build-push-action to 5 and got "no disk space" #968
Comments
This error is returned by the runner, not the action. Like actions/runner#1807
I don't think this is related. Your last build was 5 months ago so maybe now there is less space left on runner version |
Confirming that it does not seem related to docker/build-push-action. My issue seems to have been caused by either working off a upstream base image which may have grown(?) retrospectively even though I used a pinned version, or maybe more likely due to lower disk space available these days on the latest ubuntu runners when compared to five months ago. I used this 4 minute step to free up 23 Gb disk space on the runner after the checkout step: -
name: Free disk space on Ubuntu runner 🔧
uses: kfir4444/free-disk-space@main
with:
# frees about 6 GB, warning: may remove required tools
tool-cache: false
android: true
dotnet: true
haskell: true
large-packages: true
swap-storage: true @crazy-max thanks so much for those pointers, you saved my day (again), the build is green and now I can get out and mill some real logs instead of slicing through text logs :) Thinking that an official "docker/buildx-ubunturunner-freespace" step that removes all extra stuff not required for running a build-x job on a standard runner would be nice, 23 Gb is a substantial portion of the total available space! |
Contributing guidelines
I've found a bug, and:
Description
I just merged a dependabot PR to upgrade docker/build-push-action to 5 at https://github.com/KTH-Library/kontarion/blob/master/.github/workflows/push-kontarion.yml.
The previous build status was green but after merging the PR, the job fails with a "no disk space" annotation.
Expected behaviour
Bumping the version number for docker/build-push-action to 5 (dependabot also wanted to bump docker/setup-buildx-action, docker/metadata-action and docker/login-action one step up) was the only change since the previous succesful/green build, see https://github.com/KTH-Library/kontarion/actions/runs/4754371976.
So the expectation was to not see "no disk space" reported.
Actual behaviour
This annotation was shown:
Repository URL
https://github.com/KTH-Library/kontarion
Workflow run URL
https://github.com/KTH-Library/kontarion/actions/runs/6194704763/job/16818117829
YAML workflow
Workflow logs
logs_5.zip
BuildKit logs
No response
Additional info
The "no disk space" issue is similar to #238 - ie no logs but an "annotation" describes the issue.
Unclear what to do - can I clear out disk space somehow? Clear some caches?
How can I understand how to fix the issue?
Can/should my YAML workflow file be improved to avoid the "no disk space" issue?
The text was updated successfully, but these errors were encountered: