ci: fix faulty bin-image job

[crazy-max]

relates to https://github.com/docker/buildx/actions/runs/13643604134/job/38138677210

System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250304-005208-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.OSFileStreamStrategy.Write(ReadOnlySpan`1 buffer)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
   at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
   at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
   at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250304-005208-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.OSFileStreamStrategy.Write(ReadOnlySpan`1 buffer)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
   at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
   at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
   at GitHub.Runner.Common.Tracing.Error(Exception exception)
   at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.322.0/_diag/Worker_20250304-005208-utc.log'
   at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
   at System.IO.Strategies.OSFileStreamStrategy.Write(ReadOnlySpan`1 buffer)
   at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   at System.Diagnostics.TextWriterTraceListener.Flush()
   at System.Diagnostics.TraceSource.Flush()
   at GitHub.Runner.Common.Tracing.Dispose(Boolean disposing)
   at GitHub.Runner.Common.Tracing.Dispose()
   at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
   at GitHub.Runner.Common.TraceManager.Dispose()
   at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
   at GitHub.Runner.Common.HostContext.Dispose()
   at GitHub.Runner.Worker.Program.Main(String[] args)

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

[crazy-max]

Ah brownout of ubuntu-20.04 actions/runner-images#11101

[tonistiigi]

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?

[crazy-max]

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.

[tonistiigi]

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.

[crazy-max]

I don't understand how building small cli binary could run out of space.

Added repro in last commit temporarily: 69e83b7

See https://github.com/docker/buildx/actions/runs/13699603058/job/38315229163

I did see this fail in PR as well but I've lost the link.

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

if: ${{ github.event_name != 'pull_request' && github.repository == 'docker/buildx' }}

[tonistiigi]

I still would like to understand

• How much space Github gives us
• How much do we use
• Where do we use it

[crazy-max]

• How much space Github gives us

According to https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories we have 14GB available.

• How much do we use
• Where do we use it

As we got a system exception on the runner we can't collect traces but I can check locally how much this build requires.