Closed plleg closed 10 months ago
I am having similar issues related to this ticket.
This is what I see in the logs (via docker logs):
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (7) Failed to connect to localhost port 8080 after 4 ms: Couldn't connect to server % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (6) Could not resolve host: updateVersion
That should make sure that Hamclock is up to date if youre not rebuilding the container image every time. However, since this didnt work for me either, I've removed it for the time being.
It probably didn't work because the API isn't active while HamClock is prompting for setup.
It probably didn't work because the API isn't active while HamClock is prompting for setup.
That's a very good reason.
What is updateVersion ?
What is the purpose of (run.sh): curl localhost:8080 updateVersion
Even if I remove that line, the container still stops. Details shows two related lines: