Public | Automated Build

Last pushed: 2 years ago
Short Description
Garbage collector for docker containers and images. Fork spotify/docker-gc w/ more features
Full Description

docker-gc

A simple Docker container and image garbage collection script.

  • Containers that exited more than an hour ago are removed.
  • Images that don't belong to any remaining container after that are removed.

Although docker normally prevents removal of images that are in use by
containers, we take extra care to not remove any image tags (e.g., ubuntu:14.04,
busybox, etc) that are in use by containers. A naive docker rmi $(docker images -q) will leave images stripped of all tags, forcing docker to re-pull the
repositories when starting new containers even though the images themselves are
still on disk.

This script is intended to be run as a cron job, but you can also run it as a Docker
container (see below).

Building the Debian Package

$ apt-get install git devscripts debhelper
$ git clone https://github.com/spotify/docker-gc.git
$ cd docker-gc
$ debuild -us -uc -b

If you get lintian errors during debuild, try debuild --no-lintian -us -uc -b.

Installing the Debian Package

$ dpkg -i ../docker-gc_0.0.4_all.deb

This installs the docker-gc script into /usr/sbin. If you want it to
run as a cron job, you can configure it now by dropping a file like this
into /etc/cron.hourly/.

#!/bin/bash
/usr/sbin/docker-gc

Manual Usage

To use the script manually, run docker-gc. The system user under
which docker-gc runs needs to have read and write access to
the $STATE_DIR environment variable which defaults to /var/lib/docker-gc.

Excluding Images From Garbage Collection

There can be images that are large that serve as a common base for
many application containers, and as such, make sense to pin to the
machine, as many derivative containers will use it. This can save
time in pulling those kinds of images. There may be other reasons to
exclude images from garbage collection. To do so, create
/etc/docker-gc-exclude, or if you want the file to be read from
elsewhere, set the EXCLUDE_FROM_GC environment variable to its
location. This file can contain image name patterns (in the grep
sense), one per line, such as spotify/cassandra:latest or it can
contain image ids (truncated to the length shown in docker images
which is 12.

An example image excludes file might contain:

spotify/cassandra:latest
9681260c3ad5

You can also provide excluded images via environment variable $EXCLUDE_IMAGES
like:

docker run -e "$EXCLUDE_IMAGES=alpine busybox" ...

Excluding Containers From Garbage Collection

There can also be containers (for example data only containers) which
you would like to exclude from garbage collection. To do so, create
/etc/docker-gc-exclude-containers, or if you want the file to be
read from elsewhere, set the EXCLUDE_CONTAINERS_FROM_GC environment
variable to its location. This file should container name patterns (in
the grep sense), one per line, such as mariadb-data.

An example container excludes file might contain:

mariadb-data
drunk_goodall

You can also provide containers to be excluded via environment
variable $EXCLUDE_CONTAINERS like:

docker run -e "$EXCLUDE_CONTAINERS=data mysql" ...

Dry Run

If you want to do a dry run and see what will be deleted without actually
really deleting images or containers you can use the DRY_RUN-flags:

DRY_RUN=true docker-gc

the above will do a dry run for both containers and images.

DRY_RUN_CONTAINERS=true docker-gc

The above does a dry run only on containers. The flag alone can therefore be used in order to exclude the deletion of containers and only delete images.

DRY_RUN_IMAGES=true docker-gc

the above does a dry run only on images. The flag alone can therefore be used in order to exclude the deletion of images and only delete containers.

All environment variables

Below you find all environment variables you can use and their default value.

  • LOG_TO_SYSLOG - 0 or 1
  • SYSLOG_FACILITY - Defaults to "user"
  • SYSLOG_LEVEL - Defaults to "info"
  • SYSLOG_TAG - Defaults to "docker-gc"
  • DRY_RUN - Defaults to "false". Sets DRY_RUN_CONTAINERS and DRY_RUN_IMAGES in one option.
  • DRY_RUN_CONTAINERS - Defaults to "false"
  • DRY_RUN_IMAGES - Defaults to "false"
  • EXCLUDE_IMAGES - Space separated list of images to exclude
  • EXCLUDE_CONTAINERS - Space separated list of containers to exclude

Running as a Docker Image

A Dockerfile is provided as an alternative to a local installation. By default
the container will start up, run a single garbage collection, and shut down.

Building the Docker Image

The image is currently built with Docker 1.6.2, but to build it against a newer
Docker version (to ensure that the API version of the command-line interface
matches with your Docker daemon), simply edit the ENV DOCKER_VERSION line in
Dockerfile
prior to the build step below.

Build the Docker image with make -f Makefile.docker image or:

docker build -t docker-gc .

Running as a Docker Container

The docker-gc container requires access to the docker socket in order to
function, so you need to map it when running, e.g.:

$ docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v /etc:/etc docker-gc

You can of course pass any environment variables to the container. The example below shows how to run docker-gc in dry run mode:

$ docker run --rm -e "DRY_RUN=true" -v /var/run/docker.sock:/var/run/docker.sock -v /etc:/etc docker-gc

The /etc directory is also mapped so that it can read any exclude files
that you've created.

Docker Pull Command
Owner
eeacms
Source Repository

Comments (0)