You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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
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
The text was updated successfully, but these errors were encountered: