Docker部署Flask+MongoDB时WiredTiger启动失败求助

Hey there, looking at your error logs and Docker Compose config, your MongoDB container is hitting two linked issues with the WiredTiger storage engine: file existence conflicts and permission denied errors, which cause it to restart repeatedly and spawn those WiredTiger.wt.# zero-byte files. Let's break down how to fix this step by step:

Core Problem Breakdown #

From the logs, the key clues pointing to the root issues are:

• error:17 (File exists): MongoDB detects an existing but corrupted WiredTiger.wt file on startup, tries to rename it, but can't create a fresh working file
• error:1 (Operation not permitted): The MongoDB process inside the container doesn't have read/write permissions on the mounted /data/db directory—this is the main blocker

Step-by-Step Solutions #

1. Fix Host Directory Permissions #

The official MongoDB image runs as the mongodb user (UID/GID 999) by default. If your host's ./mongodb/data directory is owned by root or another user the container can't access, this triggers permission errors. Fix it with these commands:

# First, stop and remove the problematic MongoDB container
docker-compose stop mongodb
docker-compose rm mongodb

# Update permissions on the host data directory to match the container's user
sudo chown -R 999:999 ./mongodb/data

2. Clean Up Corrupted WiredTiger Files #

Previous crashes left behind broken storage files that MongoDB can't properly use. Let's clean them up (back up first if you need to preserve any recoverable data):

# Optional but recommended: Back up current data before cleaning
cp -r ./mongodb/data ./mongodb/data_backup

# Delete all broken WiredTiger-related files
rm -rf ./mongodb/data/WiredTiger* ./mongodb/data/journal ./mongodb/data/*.wt

3. Tweak Docker Compose for Stability (Optional) #

Add a user directive to the MongoDB service to explicitly use the correct UID/GID, preventing permission issues from recurring:

version: '2'
services:
  mongodb:
    image: mongo
    restart: always
    container_name: mongodb
    ports:
      - 27017:27017
    volumes:
      - ./mongodb/data:/data/db
    # Explicitly run as the mongodb user (UID/GID 999)
    user: "999:999"
  flask-service:
    build:
      context: ./flask
    restart: always
    container_name: flask
    depends_on:
      - mongodb
    ports:
      - 5000:5000
    environment:
      - "MONGO_HOSTNAME=mongodb"

4. Check Host Security Restrictions (If Previous Steps Fail) #

On Linux systems, AppArmor or SELinux might block container access to host directories:

• AppArmor: Temporarily loosen restrictions for testing (adjust rules properly in production):

  sudo aa-complain /etc/apparmor.d/docker
  

• SELinux: Temporarily disable it to test, then apply a permanent context for the data directory:

  # Test with SELinux disabled
  sudo setenforce 0
  
  # If that works, apply the correct SELinux context permanently
  sudo chcon -Rt svirt_sandbox_file_t ./mongodb/data
  

Restart the Services #

Once you've completed the steps above, fire up your containers again:

docker-compose up -d

MongoDB should now successfully initialize the WiredTiger engine without permission or file conflicts.

内容的提问来源于stack exchange，提问作者Tasos500