cadvisor dockerfile healthchecks do not utilize correct port if --port command is used to change from default 8080

[JerrettDavis]

The Dockerfile utilizes a static port 8080 for the healthcheck and expose operations:

cadvisor/deploy/Dockerfile

Line 68 in 255cff7

ENV CADVISOR_HEALTHCHECK_URL=http://localhost:8080/healthz

If a non-default port is utilized, users have to explicitly set the CADVISORT_HEALTHCHECK_URL environment variable to reflect the updated port otherwise the status will remain "unhealthy".

  cadvisor:
    image: gcr.io/cadvisor/cadvisor:latest
    container_name: cadvisor
    command:
      - '-port=9092'
    expose:
      - 9092
    ports:
      - 9092:9092
    environment:
      - 'CADVISOR_HEALTHCHECK_URL=http://localhost:9092/healthz'

[middleagedman]

Hello from the future.

Came here to see same issue.. Thanks for the environment string

[theanurin]

+1

[lev-blit]

to further expand on this - if you specify -url_base_prefix the healthcheck url doesn't take that into consideration, from the same exact reason

[frozenfoxx]

Came here to say the same thing, passing the environment variable override works for a healthcheck issue I was having.

[Retr0-01]

+1 still an issue up to this date

[alexis-vannot]

I confirm, the issue is still present 👍

    command:
      - '--url_base_prefix=/cadvisor'
    environment:
      - 'CADVISOR_HEALTHCHECK_URL=http://localhost:8080/cadvisor/healthz'
    labels:
      - traefik.enable=true
      - traefik.docker.network=webgateway-traefik
      - traefik.http.routers.cadvisor-router.rule=Host(`monitoring-XXX.YYYY`) && PathPrefix(`/cadvisor`)```

[dylandacosta8]

Had the same issues when setting cadvisor up on a non-default port this week. Got a fix in #3789. You won't need to change the CADVISOR_HEALTHCHECK_URL envVar, if the PR is approved and merged, it should be taken care of behind the scenes.