Cadvisor not showing Docker containers with Docker for Mac

[anantMulesoft]

Dear CAdvisor team,

I am running Docker for Mac and have two containers running on my machine as shown below:

$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
38d9770aafd4 google/cadvisor "/usr/bin/cadvisor -l" 5 minutes ago Up 5 minutes 0.0.0.0:8080->8080/tcp cadvisor
32bff84b713a tutum/hello-world "/bin/sh -c 'php-fpm " 13 minutes ago Up 5 minutes 80/tcp goofy_einstein

However, when I log into the CAdvisor Web UI on localhost:8080 and click on Docker Containers I get the following error:

Cannot connect to the Docker daemon. Is the docker daemon running on this host?

Can you please let me know what is missing or whether this is a bug?

[ebuildy]

How did you run cadvisor?

For me:

 docker run \
  --volume=/:/rootfs:ro \
  --volume=/var/run:/var/run:rw \
  --volume=/sys:/sys:ro \
  --volume=/var/lib/docker/:/var/lib/docker:ro \
  --publish=8080:8080 \
  --detach=true \
  --name=cadvisor \
  google/cadvisor:latest

works fine.

[muralibala]

How do I run cAdvisor on a different port. I have Jenkins running on port 8080. This is what I have tried but i am not able to bring up the instance on 8090. TIA

sudo docker run
--volume=/:/rootfs:ro
--volume=/var/run:/var/run:rw
--volume=/sys:/sys:ro
--volume=/var/lib/docker/:/var/lib/docker:ro
--publish=8090:8080
--name=cadvisor
google/cadvisor:latest

[mohammedna]

docker run
--volume=/:/rootfs:ro
--volume=/var/run:/var/run:rw
--volume=/sys:/sys:ro
--volume=/var/lib/docker/:/var/lib/docker:ro
--publish=8090:8080
--detach=true
--name=cadvisor
google/cadvisor:latest

This works for me as well, make sure the port 8090 is not being blocked..

[SpyMachine]

I'm having this same problem MacOS 10.15.7 and Docker Desktop 2.4.0.0

[muhammedbasilsk]

@SpyMachine
I am facing issue in MacOS 10.15.7 and Docker Desktop 2.4.0.0

[POD666]

+1, MacOS 10.15.5 and Docker Desktop 2.4.0.0, docker engine 19.03.13

At http://localhost:8080/docker/ I get:

failed to get docker info: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Looks like docker.sock in the mounted /var/run/ volume is a link to another location, could it be related?

# ls -la /var/run/
...
lrwxr-xr-x    1 root     root            79 Oct  4 14:48 docker-cli.sock -> /Users/<user>/Library/Containers/com.docker.docker/Data/docker-cli.sock
lrwxr-xr-x    1 root     root            75 Oct  4 14:48 docker.sock -> /Users/<user>/Library/Containers/com.docker.docker/Data/docker.sock

! UPD: Mounting docker.sock instead of /var/run/ resolved the issue for me:

volumes:
  ...
  - /var/run/docker.sock:/var/run/docker.sock:rw
  ...

[aks8m]

@POD666 your suggestion worked for me and removed the Docker daemon error that I was getting when going to http://cadvisor:8080/docker.

I still am having issues with directly accessing cadvisor stats via a container name (e.g., http://cadvisor:8080/docker/prometheus) - rather I need to have the long ID of the prometheus container (e.g., http://cadvisor:8080/docker/xxxxxxxxxxxxxxxxxxxxxxxxxx).

[soulmachine]

I'm having the same issue on macOS Catalina 10.15.7 and Docker Desktop 2.5.0.1 with Docker engine 19.03.13

[Djiit]

@POD666 's solution fixed it for me.

[soulmachine]

@Djiit Can you share your full command?

[muhammedbasilsk]

@POD666 Awesome... It worked.

docker run -d --name=cadvisor -p 8080:8080 --volume=/var/run:/var/run:rw --volume=/sys:/sys:ro --volume=/var/lib/docker/:/var/lib/docker:ro --volume=/var/run/docker.sock:/var/run/docker.sock:rw google/cadvisor:latest

[Djiit]

@soulmachine same as @muhammedbasilsk !

[soulmachine]

Hi @Djiit and @muhammedbasilsk , the command above works, I can see my container on my MacBook now, thanks a lot!

[soulmachine]

@muhammedbasilsk I change all rw to ro, the command still seems working.

docker run -d --name=cadvisor \
  -p 8080:8080 \
  --volume=/var/run:/var/run:ro \
  --volume=/sys:/sys:ro \
  --volume=/var/lib/docker/:/var/lib/docker:ro \
  --volume=/var/run/docker.sock:/var/run/docker.sock:ro \
  google/cadvisor:latest

[priyanka-raghavan-maersk]

This fixed the issue for me as well on mac 13.1! thank you

[FavourDaniel]

adding this /var/run/docker.sock:/var/run/docker.sock:ro to my volume section worked for me, thanks everyone