Skip to content

Conversation

@yogibear54
Copy link

Problem:

  • searxng was not able to start properly due to trying to create config files
  • the log recorded permission issue with creating uwsgi.ini and also settings.yml

Solution:

  • This is most likely a permission issue? Anyway, dropping cap_drop provides more permissions for the container...
  • I encountered this on an ubuntu and popos machine - so the problem could be specific to OS

- searxng was not able to start properly due to trying to create config files
- removing cap_drop allows the container to more permissions to modify host folder/files, which appears to be required
@coleam00
Copy link
Owner

Probably is OS specific, but thanks for this Chris! Since you had a question in the solution, could you clarify if the cap_drop change does indeed fix it for Linux?

@coleam00 coleam00 added enhancement New feature or request question Further information is requested labels May 20, 2025
@PrymalInstynct
Copy link

I am running this project in Linux and I had to do this manually after starting the project for the first time. I found that searxng was in a crashed state with an error in the container log about permission denied to uwsgi.ini. That lead me to this issue in the Searxng repo, which contained the solution.

@Reaper176
Copy link

I can confirm this is an issue and that you do in fact have to remove cap-drop on first run after which you need to re-enable it for security. <3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request question Further information is requested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants