Cadvisor: Global housekeeping is constantly looking for obsolete containers

[jlec]

The global housekeeping is creating following errors in the docker daemon logs everytime it is run

Aug 31 11:05:54 admin.*****.net docker[19919]: time="2016-08-31T11:05:54.797989892+01:00" level=error msg="Handler for GET /containers/b4ed75b9bf33a16f73e0d65c8257fcc5878e7fb1ceddf0e9ba8ac92e703da842/json returned error: No such container: b4ed75b9bf33a16f73e0d65c8257fcc5878e7fb1ceddf0e9ba8ac92e703da842"

cadvisor was started with

docker \
    run -it --rm \
    --volume=/:/rootfs:ro \
    --volume=/var/run:/var/run:rw \
    --volume=/sys:/sys:ro \
    --volume=/var/lib/docker/:/var/lib/docker:ro \
    --publish=8080:8080 \
    google/cadvisor:v0.23.8

[stefanprodan]

On Ubuntu 16.04 the docker log is full of these errors, I'm getting hundreds of them per minute.

[jonathanperret]

Could this be #1572 ?

[dashpole]

1572 is included in v0.25.0. Can someone who is experiencing this confirm that this bug is fixed (or that it isnt fixed)?

[dashpole]

actually, based on docker/docker#29056 this looks like a different bug.

[shah-zobair]

I was able to solve it by:

for name in $(ls | grep -vls /var/lib/docker/containers/ | paste -sd “|” -); do rm -f /var/lib/dockershim/$name; done