$ sudo docker exec -it searxng sh -c "id"
uid=0(root) gid=0(root) groups=0(root)

container is running as root, so there shouldn’t be any permission error?

u are right its not writable, the files are read only, that is wierd

I’m opening those files with windows but the user permission inside docker shouldn’t cause that problem.

I’m scratching my head nw

user id

u are right its not writable, the files are read only, that is wierd

I tried removing cap_drop (as instructed on https://github.com/searxng/searxng-docker/issues/115) but no luck, the permission error still exists. And also there occurs a new error no python application found

Listen on [::]:8080 doesn’t give 20054, could this be the reason?

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]

SearXNG version 2025.5.16+1b08324

Use existing /etc/searxng/uwsgi.ini

Use existing /etc/searxng/settings.yml

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]

SearXNG version 2025.5.16+1b08324

Use existing /etc/searxng/uwsgi.ini

Use existing /etc/searxng/settings.yml

Listen on [::]:8080

[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini

open("/etc/searxng/uwsgi.ini"): Permission denied [core/io.c line 525]