* Janitor: new docker-cleanup image version
The initial motivation for this version bump is support for docker 1.9+
Currently volumes don't get removed properly and lead to containers to
stall at start up, which is a pain to diagnose in rancher.
ref: https://github.com/meltwater/docker-cleanup/issues/24
* janitor: add support for KEEP_CONTAINERS_NAMED feature
* janitor: document '**None**' and '**All**'
* janitor: run with privileged mode unconditionnally
According to @sshipway, it seemed to be incompatible with a lot of
docker/rancher versions.
* janitor: bump docker-cleanup image version to 1.8.0
* Janitor doen't need privileged mode nor networking
- remove "privileged: true" property
- add "net: none" property
The cleanup tasks runs entirely without networking on /var/run/docker.sock. The calling process can access the docker so it does not need to have privileged mode.
Signed-off-by: Mathias Kaufmann <me@stei.gr>
* Added boolean question for privileged mode.
Signed-off-by: Mathias Kaufmann <me@stei.gr>
Default setting to keep ALL containers protects Rancher templates where
run-once containers are used; in general Rancher will remove its own
containers where necessary.
User of Shell Wildcards allows more flexibility when specifying images to be
kept during the sweep.
