Status-Check doesn't work with docker-compose setup #357

Closed
opened 2026-04-05 16:19:27 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Skowt on 10/9/2025

Describe the bug
The docker-compose guide indicates that you start everything up with npm start, which in turn runs:
export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d $npm_config_services && npm run status-check.

The first part of the command works but the last part, npm run status-check runs bash ./Tests/Scripts/status-check.sh tries to do a curl request to the hostname, e.g. redis which fails because docker-compose puts the redis service in the private network and doesn't expose any ports. As seen here: https://github.com/OneUptime/oneuptime/blob/master/docker-compose.base.yml#L145-L156

This means that the status check stops on the first 'app', redis and loops indefinitely until its stopped.

To Reproduce
Steps to reproduce the behavior:

  1. Setup OneUptime using Docker-compose guide on Ubuntu.
  2. Run npm start as part of the guide.
  3. Note that after all services are online, the status-check continues to error out with:
App redis returned HTTP 000, retrying in 15 seconds. Usually takes few minutes to boot.

Expected behavior
Status checks are either skipped when we run the setup via Docker or are run within one of the containers that has access to the rest of the network.

Screenshots
N/A - All command line.

Desktop (please complete the following information):

  • OS: macOs Tahoe
  • Browser: Chrome
  • Version: 141

Smartphone (please complete the following information):

  • Device: N/A
  • OS: N/A
  • Browser N/A
  • Version: N/A

Deployment Type
Self-Hosted, Latest Release, Running via docker-compose on an Ubuntu node.

Additional context
I am running npm start with the --services="" flag to reduce the number of running services but redis is still included in this list.

*Originally created by @Skowt on 10/9/2025* **Describe the bug** The docker-compose guide indicates that you start everything up with `npm start`, which in turn runs: `export $(grep -v '^#' config.env | xargs) && docker compose up --remove-orphans -d $npm_config_services && npm run status-check`. The first part of the command works but the last part, `npm run status-check` runs `bash ./Tests/Scripts/status-check.sh` tries to do a `curl` request to the hostname, e.g. `redis` which fails because `docker-compose` puts the redis service in the private network and doesn't expose any ports. As seen here: https://github.com/OneUptime/oneuptime/blob/master/docker-compose.base.yml#L145-L156 This means that the status check stops on the first 'app', redis and loops indefinitely until its stopped. **To Reproduce** Steps to reproduce the behavior: 1. Setup OneUptime using [Docker-compose guide](https://oneuptime.com/docs/installation/docker-compose) on Ubuntu. 2. Run `npm start` as part of the guide. 3. Note that after all services are online, the status-check continues to error out with: ``` App redis returned HTTP 000, retrying in 15 seconds. Usually takes few minutes to boot. ``` **Expected behavior** Status checks are either skipped when we run the setup via Docker or are run within one of the containers that has access to the rest of the network. **Screenshots** N/A - All command line. **Desktop (please complete the following information):** - OS: macOs Tahoe - Browser: Chrome - Version: 141 **Smartphone (please complete the following information):** - Device: N/A - OS: N/A - Browser N/A - Version: N/A **Deployment Type** Self-Hosted, Latest Release, Running via docker-compose on an Ubuntu node. **Additional context** I am running `npm start` with the `--services=""` flag to reduce the number of running services but redis is still included in this list.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#357