nextcloud / nextcloud/whiteboard
WhiteBoard WebSocket Server Container Image HealthCheck Port ignores Config
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
The default image for the whiteboard server
ghcr.io/nextcloud-releases/whiteboard:stable
defines a health command
HEALTHCHECK --interval=30s --timeout=3s --start-period=5s --retries=3
CMD node -e "require('http').get('http://localhost:3002', (res) => { process.exit(res.statusCode === 200 ? 0 : 1) })"
If the Port is Changed with the configuration variable PORT - the check always fails.
Perhaps its possible to use the ENV Var PORT instead of 3200 ?
Thanks in advantages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the health-check definition in the ghcr.io/nextcloud-releases/whiteboard:stable image and review how it uses the PORT configuration variable. Verify that the health check succeeds when PORT is changed from its default, while still detecting an unhealthy server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100