Documentation Update: Self-Hosted MongoDB 8.2.5 Requires GLIBC_TUNABLES Environment Variable on Linux Kernel 6.19+

### 💭 Description When self-hosting Appwrite with MongoDB 8.2.5 on Linux kernel **6.19+** (e.g., kernel 7.0.0-27-generic), the `mongod` process crashes with a segmentation fault (exit code 139) immediately after startup. This issue has been reported in the Docker community and is caused by a conflict between glibc's rseq (restartable sequences) support and tcmalloc's rseq usage. ### Steps to Reproduce 1. Set up a self-hosted Appwrite instance using MongoDB 8.2.5. 2. Run on a Linux host with kernel version 6.19 or higher (e.g., 7.0.0-27-generic - Ubuntu 26.04). 3. Start the MongoDB container. 4. The container exits with code 139 (segmentation fault) shortly after startup. **Expected Behavior:** MongoDB starts successfully and remains running. **Actual Behavior:** MongoDB crashes with a segmentation fault. ### Root Cause It occurs because tcmalloc's rseq implementation conflicts with glibc's rseq support, which is enabled by default in glibc 2.35+. On newer kernels, this conflict results in a persistent crash loop. ### Solution To resolve this, set the environment variable `GLIBC_TUNABLES=glibc.pthread.rseq=1` for the MongoDB service. For Docker Compose, add the following to the MongoDB service definition: ```yaml services: mongodb: image: mongo:8.2.5 environment: - GLIBC_TUNABLES=glibc.pthread.rseq=1 # ... other configuration ``` Please update the [self-hosting documentation](https://appwrite.io/docs/advanced/self-hosting/installation) to include: 1. A note about this compatibility issue with Linux kernel 6.19+. 2. The required environment variable for MongoDB 8.2.5. ### Additional References - Docker Forum discussion: [docker-compose mongo exit code 139](https://forums.docker.com/t/docker-compose-mongo-exit-code-139/151353/10) ### Environment - **Appwrite Server:** 1.9.5 (self-hosted) - **MongoDB:** 8.2.5 - **Linux Kernel:** 7.0.0-27-generic (Ubuntu 26.04) - **Docker:** 29.1.3, build 29.1.3-0ubuntu4.1 ### 👀 Have you spent some time to check if …