Closed richard-parker closed 3 months ago
I ran your compose with no issues on my Ubuntu server. What's your operating system?
The output you shared is what I expect to see, and then I would look for HamClock at http://host-ip:83/live.html
.
Also, just for good measure, try including the spec version in your compose:
version: "3"
services:
web:
image: ghcr.io/chrisromp/hamclock-docker:latest
ports:
- "82:8080/tcp"
- "83:8081/tcp"
volumes:
- data:/root/.hamclock/
restart: unless-stopped
volumes:
data:
Closing due to lack of activity. Feel free to reopen.
Closing due to lack of activity. Feel free to reopen.
Apologies for the radio silence! I will double-check this evening and update this thread if the issue persists.
Just to update, I have redeployed this morning using your YAML, above, and then accessing on http://host-ip:83/live.html
. This now does indeed load HamClock, thank you!
It must have been down to missing the version
declaration in the docker-compose.yaml
file, though, I'm at a loss to explain why this prevented the container starting at all.
Thank you @ChrisRomp for jumping on this and helping out. Much appreciated.
Hello,
I've just attempted to run this via Docker Compose using the docker-compose.yaml below:
After a couple of minutes in the
starting
state, the container enters theunhealthy
state with the following log:Docker environment information:
Any help you could offer would be appreciated!
Thanks