-
Notifications
You must be signed in to change notification settings - Fork 510
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
ci: fix faulty bin-image job #3040
base: master
Are you sure you want to change the base?
Conversation
b9c76bd
to
99ea8c5
Compare
Ah brownout of ubuntu-20.04 actions/runner-images#11101 |
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
99ea8c5
to
4636c80
Compare
So what happened? I see it in other PR as well. Are we really using too much space (what changed) or did something happen with the runners? |
It's related to adding netbsd builds in #2901, we were close to the limit I suppose. And we have not detected this issue until it was merged because we are akipping this job on PR as it takes quite some time. With #3005 it would be enabled on PR. |
I don't understand how building small cli binary could run out of space. I did see this fail in PR as well but I've lost the link. |
Added repro in last commit temporarily: 69e83b7 See https://github.com/docker/buildx/actions/runs/13699603058/job/38315229163
Not sure how it would fail on PR as we are skipping this job entirely for this event atm: buildx/.github/workflows/build.yml Line 412 in 7b7dbe8
|
69e83b7
to
4636c80
Compare
relates to https://github.com/docker/buildx/actions/runs/13643604134/job/38138677210
We have no space left on runner for bin-image job since #2901
As quick fix we can free up disk space on the runner but would be better to distribute build in the future: #3005