CopilotKit / CopilotKit/outpost
discord-bot container reports unhealthy despite running fine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 15
Description
Problem
The outpost-discord-bot container shows (unhealthy) in docker ps, even though the bot is working — logs show:
[Discord Bot] Health check listening on port 3005
[Discord Bot] Logged in as Outpost#3827
[Discord Bot] Serving 2 guild(s)
The healthcheck listens on 3005 but the container exposes 3001 — likely a port mismatch so the healthcheck probe never hits the right port and is marked failing.
Impact
Cosmetic but noisy: false-negative health status, and any orchestration that gates on health (depends_on: condition: service_healthy) would wait/fail incorrectly.
Expected
Align the healthcheck port with the port the bot actually listens on (or vice versa).
Found during
Setup analysis (see PR #117).
Contributor guide
No contributing guide indexed for this repository
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
Inspect the container configuration for outpost-discord-bot, starting with the healthcheck and exposed-port settings described in the issue and PR #117. Compare port 3005 with port 3001, then verify the corrected health status with the container healthcheck and any orchestration behavior that depends on it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100