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.
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.
open(“/etc/searxng/uwsgi.ini”): Permission denied [core/io.c line 525]
I think here is your problem. Make sure that file exists and is readable from inside of the docker.
As someone who know pgp exists, i say have at it feds, lets see what kind of explots clippy2.0 has and how quickly it gets cracked.
Seriously ever actual expert in cryptography would tell then what they want is not possible. It would be exploited within weeks, probably by multiple different actors. Let them fuck around and find out, they obviously dont “learn” from it, but at least it will shut them down for another decade or so.