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.

  • Why “git clone” is trying to use https
  • Cannot connect to redis running as container with boot2docker
  • Can't pull kubernetes dns container from behind proxy
  • Backup Mongo in a Docker container
  • Docker - modifying IPTABLES for host from container
  • cannot pm2 list in docker containers
  • 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

  • Is there any way to display container names in docker stats?
  • Deploying ASPNET core app in IIS inside Docker Container
  • How to fake cpu architecture in docker container?
  • can not ssh to another Docker Container docker-compose
  • Crons in cron.d won't run on Ubuntu running inside Docker Container
  • CHEF provisioning: SystemStackError: stack level too deep
  • 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.