Thousands of cAdvisor Docker containers created until disk runs out of space

Google Compute Engine container-optimized VM image has a built-in cAdvisor container that gets started automatically.

In the last three days, an infinite loop started to create ~15000 containers of the cAdvisor image until the disk ran out of space.

  • Copy a file from host OS to docker image
  • Can ping intranet from host, but not from a container
  • Docker IO Error with local js file
  • Debugging .NET Core projects AND .NET libraries available in NuGet
  • impossible to delete a container
  • Running bazel with sandboxing in a Docker container
  • The versions are:

    Linux docker-04 3.16-0.bpo.2-amd64 #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64

    Docker version 1.2.0, build fa7b24f

    How can this bug be fixed?

    For a temporary fix, I’ve deleted all ~15000 containers using the following script:

    docker ps -a | grep ‘days ago’ | awk ‘{print $1}’ | xargs –no-run-if-empty docker rm

  • how to correctly remove previous commits of an image in order to build it from the very scratch
  • Pbs with python tempfile.mkdtemp in gitlab-ci docker
  • Connection issue with Docker
  • How to Bootstrap from Workstaion to Docker conatiner?
  • Bash script behaves differently from Docker run command instead of inside container itself?
  • MySQL -> .NET Core Dependency error (MySql.Data)
  • One Solution collect form web for “Thousands of cAdvisor Docker containers created until disk runs out of space”

    There was a bug in the latest cAdvisor release (0.7.0). It has been fixed since and a patch release was made (0.7.1). GCE container image should pick it up and release a new build soon.

    If you see any issues, please report them via the GitHub issue tracker.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.