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
{{ message }}
This repository has been archived by the owner on Feb 27, 2020. It is now read-only.
When the worker startup we should purge all old containers, images, volumes and networks that might have been left-over from previous executions, in case the worker previously crashed.
I propose we either (or both):
A) tag all resources with "owner": "taskcluster-worker" and any such tagged resources at startup.
B) make this a worker configuration option, that is disabled by default.
This would avoid us running out of disk space after a crash where resources were leaked.
The text was updated successfully, but these errors were encountered:
When the worker startup we should purge all old containers, images, volumes and networks that might have been left-over from previous executions, in case the worker previously crashed.
I propose we either (or both):
A) tag all resources with
"owner": "taskcluster-worker"
and any such tagged resources at startup.B) make this a worker configuration option, that is disabled by default.
This would avoid us running out of disk space after a crash where resources were leaked.
The text was updated successfully, but these errors were encountered: