Documentation missing information for anyone running mongodb v4.4 - "Error dependency database failed to start" #127

New Issue

2026-02-16T12:51:35-05:00

yindo commented

2026-02-16 12:51:35 -05:00

Originally created by @noisymuffin on GitHub (Feb 11, 2026).

What happened?

For anyone running on older hardware like myself, and following the instructions for downgrading to mongodb 4.4 by editing the compose file:

# compose.yml
services:
  database:
    image: mongo:4.4

The database will start in an unhealthy state, which affects other services that have it as a dependency. You also need to edit the database service healthcheck like so.

Before:

   healthcheck:
      test: echo 'db.runCommand("ping").ok' | mongosh localhost:27017/test --quiet

After:

   healthcheck:
      test: echo 'db.runCommand("ping").ok' | mongo localhost:27017/test --quiet

EDIT: I also had to change the image tag to a slightly older version for redis to work properly. This should probably be a separate issue but putting it here for anyone else running into the same problems:

  redis:
    image: docker.io/eqalpha/keydb:x86_64_v6.3.3
    restart: always

Originally created by @noisymuffin on GitHub (Feb 11, 2026). ### What happened? For anyone running on older hardware like myself, and following the instructions for downgrading to mongodb 4.4 by editing the compose file: ``` # compose.yml services: database: image: mongo:4.4 ``` The database will start in an unhealthy state, which affects other services that have it as a dependency. You also need to edit the database service healthcheck like so. Before: ``` healthcheck: test: echo 'db.runCommand("ping").ok' | mongosh localhost:27017/test --quiet ``` After: ``` healthcheck: test: echo 'db.runCommand("ping").ok' | mongo localhost:27017/test --quiet ``` EDIT: I also had to change the image tag to a slightly older version for redis to work properly. This should probably be a separate issue but putting it here for anyone else running into the same problems: ``` redis: image: docker.io/eqalpha/keydb:x86_64_v6.3.3 restart: always ```

yindo commented

2026-02-16 12:51:35 -05:00

@noisymuffin commented on GitHub (Feb 12, 2026):

I seem to have created this as a "bug" when it really shouldn't be, its a documentation problem.
Does anyone know if I can remove the tag? Or do I re-create this as a standard issue?

@noisymuffin commented on GitHub (Feb 12, 2026): I seem to have created this as a "bug" when it really shouldn't be, its a documentation problem. Does anyone know if I can remove the tag? Or do I re-create this as a standard issue?

yindo commented

2026-02-16 12:51:35 -05:00

@TwoStarLightMints commented on GitHub (Feb 13, 2026):

Hello, your suggest actually resolved the problem entirely for me. I did also make a change to the keydb entry, as according to other issues in its own github repo, you need to use either unstable or x86_64_v6.3.3 tags. There is some sort of issue with the latest tag.

@TwoStarLightMints commented on GitHub (Feb 13, 2026): Hello, your suggest actually resolved the problem entirely for me. I did also make a change to the keydb entry, as according to other issues in its own github repo, you need to use either unstable or x86_64_v6.3.3 tags. There is some sort of issue with the latest tag.

yindo commented

2026-02-16 12:51:35 -05:00

@noisymuffin commented on GitHub (Feb 13, 2026):

Yes I also ran into the same issue and found solutions on other forums - guess I'll add it to this Issue :)

@noisymuffin commented on GitHub (Feb 13, 2026): Yes I also ran into the same issue and found solutions on other forums - guess I'll add it to this Issue :)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#127