Permission denied for public-resolvers.md and relays.md

[xorguy]

Hi.

I have running dnscrypt-proxy with mapped volume to store dnscrypt-proxy.toml configuration file and I'm getting permission denied for both files at docker logs.

[WARNING] /config/public-resolvers.md: open sf-psizzome646u2elx.tmp: permission denied

Both files appeared at mapped volume first time I run, but why is it now showing permission denied? Both files have same user:group like configuration file.

Any way to not have those permission denied?

Thanks.

[jedisct1]

Maybe the permissions on the directory are not good?

In such a scenario, I'd just chmod 777 (yeah, I know) the directory, start the container and see what user the files were created as in order to then set proper permissions on the directory.

[klutchell]

Recently the I changed the runtime user from nonroot to nobody:nogroup so perhaps your existing configuration files still have the old permissions?

If your host OS is Linux, can you share the permissions on your config directory and files?

$ ls -al /path/to/config/

Also, @jedisct1's suggestion could work so I would try that as well.

[xorguy]

@klutchell The files where not created/owned by nobody:nogroup so almost 99% was it, even that I tried to chmod 777, from @jedisct1 comment, the folder and deleting previous files and now the files have correct user and groups and seems that it is working great with no WARNINGs.

[klutchell]

Excellent! I'll add a note to the readme that the files in the configuration volume should be either readable by world, or owned by nobody:nogroup.

Can we close this issue?

[xorguy]

Agree to close!