Skip to content

Add config option to delete container volumes for failed runners #34292

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

Closed
joestump opened this issue Apr 26, 2025 · 2 comments
Closed

Add config option to delete container volumes for failed runners #34292

joestump opened this issue Apr 26, 2025 · 2 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@joestump
Copy link

joestump commented Apr 26, 2025

Feature Description

It took me entirely too long to figure out that failed Gitea runners leave behind orphaned volumes. What I can't seem to figure out is how to get Gitea/Act to nuke these things (or harvest them periodically?). Since the containers are removed, the volumes are orphaned and immune to pruning in Docker.

It looks like Act should be deleting these? https://github.com/nektos/act/blob/master/pkg/runner/run_context.go#L353-L354

But it's not clear if Gitea has a way to enable that functionality for failed jobs.

Screenshots

# docker volume ls -q | grep '^GITEA-ACTIONS-TASK-' | wc -l
13921
@joestump joestump added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Apr 26, 2025
@TheFox0x7
Copy link
Contributor

I think this belongs to act_runner repository: https://gitea.com/gitea/act_runner

@joestump
Copy link
Author

@TheFox0x7 thank you for pointing me in the right direction. Looks like someone else reported this a couple months back. Closing this out – anyone else who sees this thread should hop on over to https://gitea.com/gitea/act_runner/issues/659

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants