Comment on Need help with searxng docker compose

• Override4414@lemmy.world ⁨2⁩ ⁨days⁩ ago

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

  source

  • HappyTimeHarry@lemm.ee ⁨2⁩ ⁨days⁩ 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

    • Override4414@lemmy.world ⁨2⁩ ⁨days⁩ ago

      SN_FR_@SN:~$ sudo docker exec -it searxng sh -c "id"
      uid=0(root) gid=0(root) groups=0(root)
      

      source

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

        The problem is that while docker is running as root (0) the searxng process internally runs as a user searxng with id 977

        So your filesystem outside of docker needs to have those files assigned the right ownership.

        This thread has a more detailed discussion that you might find helpful.

        source
• Override4414@lemmy.world ⁨2⁩ ⁨days⁩ 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 ⁨2⁩ ⁨days⁩ 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