From 8fe0b98cedfcfbde3761e0850f1a0e7b94636c6f Mon Sep 17 00:00:00 2001
From: ItsNiceCraft <74358857+ItsNiceCraft@users.noreply.github.com>
Date: Mon, 23 Jun 2025 21:47:34 +0200
Subject: [PATCH] docs: remove security cap note (#398)

---
 README.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/README.md b/README.md
index 32fdc49..3a778d1 100644
--- a/README.md
+++ b/README.md
@@ -25,9 +25,6 @@ There are two ways to host SearXNG. The first one doesn't require any prior know
    On a Mac: `sed -i '' "s|ultrasecretkey|$(openssl rand -hex 32)|g" searxng/settings.yml`
 5. Edit [searxng/settings.yml](https://github.com/searxng/searxng-docker/blob/master/searxng/settings.yml) according to your needs
 
-> [!NOTE]
-> On the first run, you must remove `cap_drop: - ALL` from the `docker-compose.yaml` file for the `searxng` service to successfully create `/etc/searxng/uwsgi.ini`. This is necessary because the `cap_drop: - ALL` directive removes all capabilities, including those required for the creation of the `uwsgi.ini` file. After the first run, you should re-add `cap_drop: - ALL` to the `docker-compose.yaml` file for security reasons.
-
 > [!NOTE]
 > Windows users can use the following powershell script to generate the secret key:
 > ```powershell