docker-compose --env "./myconfig.env" up - Command does not complete

[sodgaard]

Hi,

After updating the docker-compose.yml and running "docker-compose pull" and subsequently the above command it seems not to complete and launch VWsFriend in the background. Looking at containers VWsFriend no longer shows up. The first "docker_" are related to TeslaMate which is functioning. The "VWsFriend_" are - well obviously - related to the VWsFriend. :-)

The SSH window shows:

It seems like a new data request is sent every 5 mints triggering a new logline. However the last line does not look good.
This should just happen in the background, right?

[sodgaard]

Tried running the docker-compose file with the "-d" at the end.
A subsequent "docker ps" gives the stats (where VWsFriend is indicated as unhealthy). Also it still does not show up in the NAS Docker GUI.:

[sodgaard]

Till - could it be because the Healthcheck still explicitly refers to port 4000?

healthcheck:
      test: (wget -qO- http://localhost:4000/healthcheck | grep "ok" -q) || exit 1
      interval: 60s
      timeout: 10s
      retries: 3

/Stephen

[sodgaard]

Manually changing the port on the "test" line to the one choosen in the .env file - then it is considered healthy and shows up as a running container...

[tillsteinbach]

Yes! Thanks for the hint! I need to change that line!

[tillsteinbach]

Done