Comment on Need help with searxng docker compose

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]

• HappyTimeHarry@lemm.ee ⁨1⁩ ⁨day⁩ ago

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

  I think here is your problem.

  source

  • Override4414@lemmy.world ⁨1⁩ ⁨day⁩ ago

    I tried removing cap_drop (as instructed on 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

    source

    • HappyTimeHarry@lemm.ee ⁨1⁩ ⁨day⁩ ago

      try opening a shell with ’ docker exec -it searxng sh" and see if you can cat the file from inside docker, if yes then I’m not sure of a solution ,if no then the problem is with permissions on your filesystem outside of docker where you have " - ./data/searxng:/etc/searxng" You need to go to ./data/searxng and correct the permissions so they can be read inside the docker.

      source

      • Override4414@lemmy.world ⁨1⁩ ⁨day⁩ ago

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

        source

        • -> View More Comments
      • Override4414@lemmy.world ⁨1⁩ ⁨day⁩ ago

        ~ # ls /etc/searxng
        settings.yml  uwsgi.ini
        ~ # cat settings.yml
        cat: can't open 'settings.yml': No such file or directory
        ~ # cat /etc/searxng/settings.yml
        general:
          # Debug mode, only for development. Is overwritten by ${SEARXNG_DEBUG}
          debug: false
          # displayed name
          instance_name: "searxng"
          # For example: https://example.com/privacy
        

        I think I do have the permission?

        source

        • -> View More Comments