jandieman
/
searxng-docker
mirror of https://github.com/searxng/searxng-docker.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Explain required cap_drop removal on first run (#258) 

Add instructions to the `README.md` for removing `cap_drop: - ALL` on the first run.

* **Explanation**: Add a note explaining that `cap_drop: - ALL` must be removed from the `docker-compose.yaml` file for the `searxng` service to successfully create `/etc/searxng/uwsgi.ini`.
* **Reason**: Explain that the `cap_drop: - ALL` directive removes all capabilities, including those required for the creation of the `uwsgi.ini` file.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/IAmStoxe/searxng-docker?shareId=XXXX-XXXX-XXXX-XXXX).
This commit is contained in:
stoXe 2024-10-04 02:24:33 -07:00 committed by GitHub
parent 61745b3bf1
commit 0667030a42
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -40,6 +40,9 @@ Create a new SearXNG instance in five minutes using Docker
> (Get-Content searxng/settings.yml) -replace 'ultrasecretkey', $secretKey | Set-Content searxng/settings.yml > (Get-Content searxng/settings.yml) -replace 'ultrasecretkey', $secretKey | Set-Content searxng/settings.yml
> ``` > ```
> [!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.
## How to access the logs ## How to access the logs
To access the logs from all the containers use: `docker compose logs -f`. To access the logs from all the containers use: `docker compose logs -f`.