Write permission issue in docker when saving config

[cwjackso]

Describe the bug
When saving config through the web UI I get a permission error

To Reproduce
Steps to reproduce the behavior:

1. Go to web ui
2. Click on settings
3. Click on update
4. See following error

Expected behavior
Config is saved

[cedricve]

Interesting will check out myself. Probably because it’s copying the config directory, without setting the appropriate permissions.

…

On 18 Apr 2020, at 20:41, Carl Jackson ***@***.***> wrote: Describe the bug When saving config through the web UI I get a permission error To Reproduce Steps to reproduce the behavior: Go to web ui Click on settings Click on update See following error <https://user-images.githubusercontent.com/12407694/79662062-61007780-81ac-11ea-92ca-e04fd759df2e.png> Expected behavior Config is saved — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#159>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALZUG2BHOVTMSV3U3RVQDTRNHX7HANCNFSM4MLOWSQA>.

[cwjackso]

Haven't fully investigated yet but maybe linked - web hooks have stopped working on motion detection. Recording is still happening just not the hook. This is since changing to the latest base image (rather then amd-64) On Sat, 18 Apr 2020, 19:48 Cédric Verstraeten, <[email protected]> wrote:

…

Interesting will check out myself. Probably because it’s copying the config directory, without setting the appropriate permissions. > On 18 Apr 2020, at 20:41, Carl Jackson ***@***.***> wrote: > > > Describe the bug > When saving config through the web UI I get a permission error > > To Reproduce > Steps to reproduce the behavior: > > Go to web ui > Click on settings > Click on update > See following error > < https://user-images.githubusercontent.com/12407694/79662062-61007780-81ac-11ea-92ca-e04fd759df2e.png > > Expected behavior > Config is saved > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub < #159>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AALZUG2BHOVTMSV3U3RVQDTRNHX7HANCNFSM4MLOWSQA >. > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC6VHDRXYVSQMPSHEPOTXMLRNHYXJANCNFSM4MLOWSQA> .

[cedricve]

thanks for reporting, I will have a look.

[cedricve]

@cwjackso can you share the docker command you are running?

[cedricve]

additionally can you show the permissions of the folder you are mounting?

[cedricve]

hmm, make sure your permissions are set correctly. I was able to simulate the error if I set file permissions to 755.

Please set them to 777 to make it work.

[cwjackso]

I have updated to the latest version and this didn't change anything.

Setting 777 permission on the config directory (mounted as a volume via docker compose) has fixed the issue.

Not sure why specifically the config volume needs this though as the logs and capture files all write fine without it, and with the old docker image I never needed had that level of permission.