docker compose error

[blueman009]

Self Checks

• I have read the Contributing Guide.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Aitoearn version

2.1.0

Please select your platform

Web

Steps to reproduce

docker compose up -d
[+] Running 3/3
✔ aitoearn-ai Pulled 1.7s
✔ aitoearn-web Pulled 1.7s
✔ aitoearn-server Pulled 1.7s
[+] Running 5/5
✔ Container aitoearn-rustfs Healthy 0.5s
✔ Container aitoearn-redis Healthy 0.5s
✘ Container aitoearn-mongodb Error 0.5s
✔ Container aitoearn-mongodb-rs-init Started 0.2s
✔ Container aitoearn-rustfs-init Started 0.2s
dependency failed to start: container aitoearn-mongodb is unhealthy

✔️ Expected Behavior

mongodb error

❌ Actual Behavior

Ubuntu 24.04.1 LTS
mongodb error

[Yuuki-Sakura]

Thanks for reporting this. The container aitoearn-mongodb is unhealthy error means MongoDB failed its health check, but we need more details to identify the root cause.

Please run the following commands and share the output:

# MongoDB container logs
docker logs aitoearn-mongodb

# Health check status
docker inspect aitoearn-mongodb --format='{{json .State.Health}}' | jq .

# System info
uname -m
free -h
docker --version

Common causes on Ubuntu:

• ARM architecture — MongoDB 5+ requires x86_64 or ARM64
• Insufficient memory — MongoDB needs at least 1GB free RAM
• AVX support missing — MongoDB 5+ requires AVX on x86_64 (grep avx /proc/cpuinfo)

[blueman009]

docker inspect aitoearn-mongodb --format='{{json .State.Health}}' | jq .
{
"Status": "unhealthy",
"FailingStreak": 0,
"Log": []
}

root@iZ6we2aqxcjqbql9r1s4mpZ:/AiToEarn# uname -m
x86_64
root@iZ6we2aqxcjqbql9r1s4mpZ:/AiToEarn# free -h
total used free shared buff/cache available
Mem: 7.1Gi 4.1Gi 396Mi 3.7Mi 3.0Gi 3.0Gi
Swap: 0B 0B 0B
root@iZ6we2aqxcjqbql9r1s4mpZ:~/AiToEarn# docker --version
Docker version 28.4.0, build d8eb465

mongo.zip

[Yuuki-Sakura]

Thanks for the logs! The root cause is clear — it's a MongoDB version incompatibility issue.

Your MongoDB data volume was created with MongoDB 7.0, but the current docker-compose.yml uses mongo:latest which is now 8.2. MongoDB does not support skipping major versions during upgrades, so it fails with:

UPGRADE PROBLEM: Found an invalid featureCompatibilityVersion document
version: "7.0" ... Expected one of: '8.2', '8.1', '8.0'

Solution A: Reset data volume (simple, loses MongoDB data)

docker compose down
docker volume rm aitoearn_mongodb-data aitoearn_mongodb-config
docker compose up -d

Solution B: Upgrade path (preserves data)

You need to upgrade 7.0 → 8.0 → 8.2 step by step:

# 1. Stop current containers
docker compose down

# 2. Start MongoDB 8.0 temporarily to migrate data
docker run -d --name mongo-upgrade \
  -v aitoearn_mongodb-data:/data/db \
  -v aitoearn_mongodb-config:/data/configdb \
  -e MONGO_INITDB_ROOT_USERNAME=admin \
  -e MONGO_INITDB_ROOT_PASSWORD=password \
  --entrypoint bash \
  mongo:8.0 -c "openssl rand -base64 756 > /data/mongodb-keyfile && chmod 400 /data/mongodb-keyfile && chown mongodb:mongodb /data/mongodb-keyfile && exec docker-entrypoint.sh mongod --replSet rs0 --keyFile /data/mongodb-keyfile --bind_ip_all"

# 3. Wait ~30s for startup, then upgrade featureCompatibilityVersion
docker exec -it mongo-upgrade mongosh -u admin -p password --authenticationDatabase admin --eval 'db.adminCommand({setFeatureCompatibilityVersion: "8.0", confirm: true})'

# 4. Remove temp container
docker stop mongo-upgrade && docker rm mongo-upgrade

# 5. Start with 8.2 (latest)
docker compose up -d

For most users, Solution A is recommended unless you have important data to preserve.