[Question]: Docker MongoDB container "Operation not permitted" error on WSL 2 Windows 11

[lam584]

What is your question?

I'm encountering a persistent "Operation not permitted" error when attempting to start a MongoDB container with Docker on Windows 11 using WSL 2. The MongoDB container is set to use a mounted volume from the Windows filesystem (/mnt/d/LibreChat/data-node). Despite the directory and its files showing full read-write-execute (rwxrwxrwx) permissions when checked from the WSL terminal, MongoDB fails to start, citing permission issues.

More Details

Environment

• OS: Windows 11 22631.3235
• Docker Desktop Version: 4.27.2 (137060)
• WSL Version: 2
• MongoDB Docker Image Version: Latest (as of date of issue posting)
• Issue encountered on: /mnt/d/LibreChat/data-node

Description

I'm encountering a persistent "Operation not permitted" error when attempting to start a MongoDB container with Docker on Windows 11 using WSL 2. The MongoDB container is set to use a mounted volume from the Windows filesystem (/mnt/d/LibreChat/data-node). Despite the directory and its files showing full read-write-execute (rwxrwxrwx) permissions when checked from the WSL terminal, MongoDB fails to start, citing permission issues.

Steps to Reproduce

1. Navigate to the directory containing the docker-compose.yml.
2. Run docker compose up.
3. MongoDB container fails to start with an "Operation not permitted" error.

Expected Behavior

MongoDB container starts successfully, accessing and manipulating data within the specified directory without permission issues.

Actual Behavior

MongoDB fails to start, with log output suggesting permission-related errors accessing its data directory mounted from the Windows file system.

Additional Context

• I have verified that the directory and files at /mnt/d/LibreChat/data-node have rwxrwxrwx permissions (using ls -l), and the owner is root.
• Here is a snippet of the MongoDB related section from my docker-compose.yml:

  mongodb:
    container_name: chat-mongodb
    image: mongo
    restart: always
    volumes:
      - ./data-node:/data/db
    command: mongod --noauth

• I have checked Docker and WSL settings regarding file sharing and permissions but found no clues pointing to the cause of this issue.

Given these points, it seems the problem might be related to how Docker/WSL 2 handles permissions for Windows filesystem-mounted volumes, or a specific interaction with the MongoDB container. Any assistance or insights from the community would be greatly appreciated!

Thank you!

What is the main subject of your question?

Installation

Screenshots

Code of Conduct

• I agree to follow this project's Code of Conduct

[james-williams0]

Also observing a similar issues with a similar environment, using the docker-compose.yml as included with the LibreChat repo and its own chat-mongodb container.

Environment:

• Windows 11 23H2 Build 22631.3235
• Docker Desktop 4.28.0 (139021)
• WSL 2
• Commit hash 0f417aae

Pulled the following logs out which seem relevant:

chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.774+00:00"},"s":"I",  "c":"WT",       "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":{"ts_sec":1710198755,"ts_usec":773993,"thread":"1:0x7fb38f50dc80","session_name":"connection","category":"WT_VERB_BLOCK","category_id":3,"verbose_level":"NOTICE","verbose_level_id":-1,"msg":"unexpected file WiredTiger.wt found, renamed to WiredTiger.wt.17"}}}
chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.774+00:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":1,"message":{"ts_sec":1710198755,"ts_usec":774925,"thread":"1:0x7fb38f50dc80","session_name":"connection","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__posix_open_file:815:/data/db/WiredTiger.wt: handle-open: open","error_str":"Operation not permitted","error_code":1}}}
chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.776+00:00"},"s":"W",  "c":"STORAGE",  "id":22347,   "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.776+00:00"},"s":"F",  "c":"STORAGE",  "id":28595,   "ctx":"initandlisten","msg":"Terminating.","attr":{"reason":"1: Operation not permitted"}}
chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.776+00:00"},"s":"F",  "c":"ASSERT",   "id":23091,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28595,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":676}}
chat-mongodb      | {"t":{"$date":"2024-03-11T23:12:35.776+00:00"},"s":"F",  "c":"ASSERT",   "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}
chat-mongodb exited with code 14

[james-williams0]

For completeness, I've gone back and tried it with it commented, same result.

[fuegovic]

if they were uncommented, then try commenting them out instead

[fuegovic]

ok... one or the other often fix WiredTiger issue, tbh I'm not sure what's the solution in your case then

[lam584]

I have tried to uncomment UID and GID, but it cannot solve the problem.

[james-williams0]

I have successfully worked around my issue by cloning and running it under an Ubuntu 22.04 install on WSL, with the UID and GID commented in the .env file, using the Linux installation guide.

[halllo]

I am running podman on Windows and had the same MongoDB error:

"category_id":12,"verbose_level":"ERROR","verbose_level_id":-3,
"msg":"__posix_open_file:924:/data/db/WiredTiger.wt: handle-open: open",
"error_str":"Operation not permitted","error_code":1

Its reproducible independent of LibreChat:

podman run -d -v ./dn:/data/db mongo mongod --noauth

This summary about podman-mongodb helped me understand the situation better. So I was able to make mongodb work with --userns keep-id:

podman run -d --name self_mongodb --userns keep-id -v ./dn:/data/db mongo mongod --noauth

I added this to the docker-compose.override.yml:

services:
  mongodb:
    userns_mode: "keep-id"

Unfortunately now LibreChat could not be composed anymore:

234e06dbdaca3f5e73be8b8439996c8d19670cfcd1830b6689ddeebbed89d1d2
Error: --userns and --pod cannot be set together
...

But then I found containers/podman-compose#166 and --in-pod. So with the following command I was finally able to start up LibreChat with podman rootless containers using podman-compose on Windows:

uvx podman-compose --in-pod false up -d