Skip to content

RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.

Doc: macOS(arm64) not supported now (#20644)

Jin Haib35701065b13
diff --git a/docs/faq.mdx b/docs/faq.mdx
index 0b9e584f4c..41fa377ca4 100644
--- a/docs/faq.mdx
+++ b/docs/faq.mdx
@@ -262,7 +262,7 @@ A running container does not necessarily mean that the service inside it is heal
The status of a Docker container does not necessarily reflect the status of the service inside it. A service can be unhealthy even when its container is up and running. Possible causes include network failures, incorrect ports, and DNS or configuration errors.
:::
-3. If your container keeps restarting, ensure `vm.max_map_count` >= 262144. On Linux, update **/etc/sysctl.conf** to keep the change permanent. For macOS, see the following FAQ.
+3. If your container keeps restarting, ensure `vm.max_map_count` >= 262144. On Linux, update **/etc/sysctl.conf** to keep the change permanent.
---
@@ -272,51 +272,6 @@ On Linux, an insufficient `vm.max_map_count` value is a common cause. Check the
---
-### How do I configure `vm.max_map_count` on macOS?
-
-`vm.max_map_count` is a Linux kernel parameter required only by Elasticsearch. It does not affect RAGFlow deployments that use Infinity as the document engine.
-
-On Docker Desktop, set the value in its Linux virtual machine:
-
-```bash
-docker run --rm --privileged alpine sysctl -w vm.max_map_count=262144
-```
-
-This setting is temporary and is reset when Docker Desktop restarts.
-
-On Colima, check the current value inside its virtual machine:
-
-```bash
-colima ssh -- sysctl vm.max_map_count
-```
-
-To set the value temporarily:
-
-```bash
-colima ssh -- sudo sysctl -w vm.max_map_count=262144
-```
-
-For a persistent setting, run `colima start --edit` and add a provision script to `colima.yaml`:
-
-```yaml
-provision:
- - mode: system
- script: |
- #!/bin/bash
- sysctl -w vm.max_map_count=262144
-```
-
-Then restart Colima:
-
-```bash
-colima stop
-colima start
-```
-
-*Contributed by [@helloxjade](https://github.com/helloxjade).*
-
----
-
### Why does the Go API return a 404 response?
The Go API returns HTTP 404 with `Not Found: <path>` when a request does not match a route. Your URL may point to the wrong service.