Feature #12900
Updated by Tom Clegg almost 5 years ago
Before downloading & installing the image for the current container, crunch-run should: * Check current usage (size In #12845 we are thinking that getting rid of docker images already present on cleaner service and implement the worker) functionality to crunch run: * Check whether Clean up the image for the current container after is already installed; if not, add the estimated image size to the current usage figure done, * Check whether any other crunch-run processes are running (if so, skip cleanup to avoid races where an image is deleted between "download" and "start" -- or handle Mark the race in container with @arv edit uuid@ some other way) attribute that prevents clean up (for debugging and investigation) * Delete old images This should have a similar functionality as needed aarvados docker cleaner. Which takes in account a max size to ensure current usage ≤ maximum * Don't delete images needed for use from the current container configuration. This feature eliminates the need for the docker-cleaner service, so we also need to * Remove docker-cleaner from the install docs * Add "uninstall docker-cleaner" to the upgrade notes * Remove docker-cleaner parts from package build/test scripts * Remove docker-cleaner from the source tree Ops will require a Docker API calls. That can temporarily disable cleanup by putting the worker in "hold" state: new containers won't be scheduled, so cleanup won't run. later expanded for other things.