slackware/ci-tools
slackware/ci-tools
3
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

WIP: Update .forgejo/workflows/reusable-build.yml #1

Closed
rizitis wants to merge 1 commit from (deleted):clean-up into main
pull from: (deleted):clean-up
merge into: slackware:main
Conversation 2 Commits 1 Files changed 1 +9
rizitis commented 2026-05-21 12:23:15 +02:00
First-time contributor
Copy link

RUNNER HOST MAINTENANCE NOTE (for the runner administrator):

The per-job cleanup above removes dangling objects after each build, but
over time unused tagged images (e.g. old slackware-builder tags) and
volumes can still accumulate on the host.
As resault user workflows will terminate on top ""No space left on device" on the runner".

It is recommended to schedule a periodic cleanup on the runner host itself.
Add the following: crontab -e

0 3 * * * docker system prune -af 2>&1 | logger -t docker-prune

This runs nightly at 03:00, removes all unused images and build cache,
and logs the output via syslog. It is safe to run while jobs are active
because Docker will not remove images currently in use

RUNNER HOST MAINTENANCE NOTE (for the runner administrator): The per-job cleanup above removes dangling objects after each build, but over time unused tagged images (e.g. old slackware-builder tags) and volumes can still accumulate on the host. As resault user workflows will terminate on top ""No space left on device" on the runner". It is recommended to schedule a periodic cleanup on the runner host itself. Add the following: crontab -e 0 3 * * * docker system prune -af 2>&1 | logger -t docker-prune This runs nightly at 03:00, removes all unused images and build cache, and logs the output via syslog. It is safe to run while jobs are active because Docker will not remove images currently in use
RUNNER HOST MAINTENANCE NOTE (for the runner administrator):

The per-job cleanup above removes dangling objects after each build, but
over time unused tagged images (e.g. old slackware-builder tags) and
volumes can still accumulate on the host.
As resault user workflows will terminate on top ""No space left on device" on the runner".

It is recommended to schedule a periodic cleanup on the runner host itself.
Add the following: crontab -e

  0 3 * * * docker system prune -af 2>&1 | logger -t docker-prune

This runs nightly at 03:00, removes all unused images and build cache,
and logs the output via syslog.  It is safe to run while jobs are active
because Docker will not remove images currently in use
rizitis closed this pull request 2026-05-31 02:20:23 +02:00
alienbob commented 2026-06-20 21:33:02 +02:00
Owner
Copy link

Hi rizitis,
Apologies for the delay in answering.
I implemented a daily cron job two weeks ago which prunes everything that's older than two days.

Hi rizitis, Apologies for the delay in answering. I implemented a daily cron job two weeks ago which prunes everything that's older than two days.
rizitis commented 2026-06-21 09:48:45 +02:00
Author
First-time contributor
Copy link

np thank you!

np thank you!

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
slackware/ci-tools!1
No description provided.