Specific type of DOCKER_HOSTNAME seems to crash the Docker Stats integration

I need help determining if this is a real bug, or just a user config error. If this is a real bug, then I'll add a bug report to the github.

I have 3 x docker hosts, each with docker socket proxies that feed into Homarr. The Docker Stats integration in Homarr shows me what's going on with my containers. So far, so good.

My socket proxies all have hostnames that end with

.internal

.internal

, eg.

hostname: socket-proxy-pve.internal

hostname: socket-proxy-pve.internal

In my Homarr compose, I have

environment:
  - DOCKER_HOSTNAMES=socket-proxy-pve,socket-proxy-truenas,socket-proxy2-pve
  - DOCKER_PORTS=2375,2375,2375

environment:
  - DOCKER_HOSTNAMES=socket-proxy-pve,socket-proxy-truenas,socket-proxy2-pve
  - DOCKER_PORTS=2375,2375,2375

and it works well

BUT, if I change any one of the hostnames to their true hostname with

.internal

.internal

then all of the hostnames will fail to be read by Docker Stats

eg. This will stop Docker Stats from showing anything:

DOCKER_HOSTNAMES=socket-proxy-pve**.internal**,socket-proxy-truenas,socket-proxy2-pve

DOCKER_HOSTNAMES=socket-proxy-pve**.internal**,socket-proxy-truenas,socket-proxy2-pve

So will this:

DOCKER_HOSTNAMES=socket-proxy-pve.**internal**,socket-proxy-truenas.**internal**,socket-proxy2-pve.**internal**

DOCKER_HOSTNAMES=socket-proxy-pve.**internal**,socket-proxy-truenas.**internal**,socket-proxy2-pve.**internal**

I can use .internal on other containers that I proxy the docker socket to. Just not Homarr (or at least not the Docker Stats integration).

If I was to guess, I'd say that this is a simple parsing error, but I'm no programmer.

Does this happen to you too? Or do I likely have something misconfigured that's causing this?

Solution

I had to --force-recreate to get it to clear the bad DNS entry and use the correct hostname

Jump to solution

Specific type of DOCKER_HOSTNAME seems to crash the Docker Stats integration

Similar Threads