homepage container fail when external connection to docker host is not respondig

[UnclePhil]

Description

When one of my docker host is stopped but still present in the docker.yaml, the homepage process pass 2 or 3 time on the error and then exit the container

If I disable the entry in the docker.yaml, everything become stable

homepage version

v2.7.0 (2e5f101, 23 oct. 2026)

Installation method

Docker

Configuration

docker.yml file
===============

docker-apps6:
  host: apps6.pko.lan
  port: 2375
  swarm: true

docker-apps165:
  host: apps165.pko.lan
  port: 2375
  swarm: true

## a test host who's not always ON
docker-dcltst01:
  host: dcltst01-01.lab.pko.lan
  port: 2375
  swarm: true

Container Logs

Skipping ownership changes for /app/config

Skipping ownership changes for /app/config/logs

/app/.next already owned by correct UID/GID or running as root, skipping chown
▲ Next.js 16.4.1

• Local: http://[::1]:3000
• Network: http://[::]:3000
  ✓ Ready in 0ms
  ✓ Running next.config took 2ms
  info: kubernetes.yaml was copied to the config folder

error: Error getting services from Docker server 'docker-dcltst01': Error: connect EHOSTUNREACH 192.168.x.y:2375
at ignore-listed frames {
errno: -113,
code: 'EHOSTUNREACH',
syscall: 'connect',
address: '192.168.x.y',
port: 2375
}

Container stopped

Browser Logs

Not a browser problem,
But it's visible in the browser because the page reload at each new start

Troubleshooting

have a docker.yaml with multiple entry
Be sure that one docker host is not responding

after some test, the homepage fail (between 1 and 3 loop)

Disable the docker slot, everything become stable.

Reenable the slot, you have between 1 or 3 test and then the homepage process fail.

I suppose that the connection error trap is not ad-hoc.

[UnclePhil]

My Bad, this was not a connection error, but a memory error in the container.

All my services are limited in Mem,
And Homepage had the following definition

    replicas: 1
     resources:
       limits:
         memory: 128M
       reservations:
         memory: 64M

and even without he docker settings, it fail after some times

now i set

      replicas: 1
      resources:
        limits:
          memory: 512M
        reservations:
          memory: 128M

and the mem occupation flirt with 125mb
I suppose that some activity burst over 128 and the close the container .
I'm going to wait some times to confirm it.