-~$ sudo mkdir -p /etc/sv
-~$ cd /etc/sv
-/etc/sv$ sudo mkdir arvados-docker-cleaner; cd arvados-docker-cleaner
-/etc/sv/arvados-docker-cleaner$ sudo mkdir log log/main
-/etc/sv/arvados-docker-cleaner$ sudo sh -c 'cat >log/run' <<'EOF'
-#!/bin/sh
-exec svlogd -tt main
-EOF
-/etc/sv/arvados-docker-cleaner$ sudo sh -c 'cat >run' <<'EOF'
-#!/bin/sh
-if [ -d /opt/rh/python33 ]; then
- source scl_source enable python33
-fi
-exec python3 -m arvados_docker.cleaner --quota 50G
-EOF
-/etc/sv/arvados-docker-cleaner$ sudo chmod +x run log/run
-/etc/sv/arvados-docker-cleaner$ sudo ln -s "$(pwd)" /etc/service/
+{
+ "Quota": "10G",
+ "RemoveStoppedContainers": "always"
+}
-If you are using a different daemon supervisor, or if you want to test the daemon in a terminal window, an equivalent shell command to run arvados-docker-cleaner is:
+*Choosing a quota:* Most deployments will want a quota that's at least 10G. From there, a larger quota can help reduce compute overhead by preventing reloading the same Docker image repeatedly, but will leave less space for other files on the same storage (usually Docker volumes). Make sure the quota is less than the total space available for Docker images.
-