recordings and config root ownership

roflcoopter / viseron

Self-hosted, local only NVR and AI Computer Vision software. With features such as object detection, motion detection, face recognition and more, it gives you the power to keep an eye on your home, office or any other place you want to monitor.

MIT License

1.51k stars 155 forks source link

recordings and config root ownership #630

Closed ceewanna closed 12 months ago

ceewanna commented 1 year ago

I observe that both config and recording files/folders are taken ownership by root once, viseron docker runs. Even I include my user to docker group and run the container, the config files/folder ownership turns to root.

roflcoopter commented 12 months ago

That is correct, the recordings/config folders permission is set to match the running user. If you want to change the running user, you can do so by following these instructions: https://viseron.netlify.app/docs/documentation/installation#user-and-group-identifiers

ceewanna commented 12 months ago

From my experience so far, I haven't specified -e options but run one in systemd service (root) and the other on command line by my account user (for testing parameters). The result was both approaches turned the config folder and files into root. It didn't quite seem to follow the running user.

From your advise, I explicitly specified -e option and it turned out fine now. Thanks.