Comment on Need help with searxng docker compose
ohshit604@sh.itjust.works 1 day ago
have you checked the directory & file permissions with ls -la /Your/SearXNG/WorkingDir ?
The error is telling you that the container does not have permission to that directory/file, you can essentially bypass this with sudo chmod 777 /Your/SearXNG/WorkingDir/* and sudo chown 1000:1000 Your/SearXNG/WorkingDir/*
I think I do have permission to the directory?
~ # ls -la /etc/searxng total 72 drwx------ 1 1026 100 42 May 17 04:49 . drwxr-xr-x 1 root root 494 May 17 05:24 .. ---------- 1 root root 68667 May 17 04:49 settings.yml ---------- 1 root root 1223 May 17 04:49 uwsgi.ini
___
Taking a look at your docker-compose.yml I see this volume mount:
volumes: - /volume1/SN/Docker/searxng-stack/searxng:/etc/searxng:rw
Whereas /volume1/SN/Docker/searxng-stack/searxng is the directory on your system docker is attempting to use to store the files inside the container from /etc/searxng.
Example of a volume mount that’ll likely work better for you;
volumes: - ~/docker/config/searxng:/etc/searxng
The tilde (~) acts as your current users home directory (not root) where docker volumes should be stored.
Apologies for the poor formatting, typing this on mobile.
bladewdr@infosec.pub 1 day ago
I really do not like recommending people chmod 777 anything.
It encourages bad practices.
ohshit604@sh.itjust.works 1 day ago
I agree, hence why I left the note at the bottom of that comment, yes it does encourage bad practices but, if all OP cares about is that it works then it should be fine.
In my other comment I instructed OP to move the volume to their users home directory so they don’t run into permission issues like this again.