Bug: docker health check failing for `venus-upnp-browser`

[mman]

The HEALTHCHECK command defined in the Dockerfile uses curl to ping the web server running inside the Venus Influx Loader.

venus-influx-loader/docker/Dockerfile

Line 31 in 4a9d23d

HEALTHCHECK --interval=10s --timeout=10s --start-period=5s CMD curl -f http://localhost:8088

When the Venus Influx Loader is started in UPNP browser only mode, via https://github.com/victronenergy/venus-influx-loader/blob/main/src/bin/venus-upnp-browser.ts, it actually does not start the built in web server, and therefore its builtin health check fails.

This can be observed by examining docker ps on the example docker installation:

$ docker ps
CONTAINER ID   IMAGE                                    COMMAND                  CREATED          STATUS                      PORTS                                       NAMES
e40f916fccc5   sodaengine/venus-influx-loader:develop   "docker-entrypoint.s…"   37 minutes ago   Up 37 minutes (unhealthy)                                               venus-grafana-browser-1
81912200c4d9   sodaengine/venus-influx-loader:develop   "docker-entrypoint.s…"   37 minutes ago   Up 37 minutes (healthy)     0.0.0.0:80->8088/tcp, [::]:80->8088/tcp     venus-grafana-loader-1
8c8dc1d6fe61   sodaengine/venus-grafana:develop         "/entrypoint.sh"         3 weeks ago      Up 37 minutes               0.0.0.0:3000->3000/tcp, :::3000->3000/tcp   venus-grafana-grafana-1
f09658b51041   influxdb:1.8                             "/entrypoint.sh infl…"   7 weeks ago      Up 6 weeks (healthy)        0.0.0.0:8086->8086/tcp, :::8086->8086/tcp   venus-grafana-influxdb-1

Not a big deal at the moment, but the fact that docker container is up, yet reported as unhealthy may be a problem in the future.

Investigate how to fix it.