Comment on Need help with searxng docker compose

• 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

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

        Yep Probably you need to change ownership and/or permissions of the files outside of docker.

        I dont want to give the wrong suggestion from memory so hopefully thats enough info to get you going in the direction of a fix. Basically see what user id owns the files inside of docker, make it the same uid outside of docker in the folder you are bind mounting.

        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

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

        If you have permissions then try editibg uwsgi.ini and see if it lets you save.

        Im going from memory but i think i had a similar issue and i had to manually create the file, yours shows the file already exists but it might not be writable.

        source