the silent space hog on every ci runner (we found ours)

Nina W. · 2026-08-23T07:37:14.167Z

Weird one. The GitLab runner disk is full: [code] but when i run du sh / teh numbers don't add up to anywhere near the disk size. It's like teh space is invisible. Builds keep failing at dokcer build. i checked teh obvious folders, home directories and /tmp, and found nothing large. The disk is a single volume. Something must be holding space that du cant see, but idk how to prove it.

ci disk-space docker1 replies · 283 views · started 2 mo. ago

Nina W.
@nina_thread
41 rep · 4 posts
2 mo. ago
Weird one. The GitLab runner disk is full:
```
Disk 0 (C:)   Active time 100%
Not responding
```
but when i run du -sh /* teh numbers don't add up to anywhere near the disk size. It's like teh space is invisible. Builds keep failing at dokcer build.

i checked teh obvious folders, home directories and /tmp, and found nothing large. The disk is a single volume. Something must be holding space that du cant see, but idk how to prove it.
2
Hugo
@hugob912
28 rep · 3 posts
2 mo. ago
lol same thing happened to me check per-job workspace folders: Jenkins keeps workspace/ per job and branch, GitLab runner keeps builds/ and cache/. Old branch workspaces pile up. Jenkins has the Discard old builds setting and the Workspace Cleanup plugin; GitLab runners can use docker executor volumes that get cleaned with clear-docker-cache. lmk how it goes

2 7 helpful

Reply to this topic