## Summary Not entirely clear on this one... In a setup where linkahead is executed as root, and the server profile with usersources.ini and `local_users: true` directory is owned by root, I couldn't start linkahead unless I added `user_group: 0:0` to my profile.yml due to missing write permissions. This happened after updating to LinkAhead 0.15.0 so it is probably related to the change of the chmod commands that we did when downsizing the image. Before, permissions were changed to 777 inside docker, which seems not to be the case anymore. ## Expected Behavior LinkAhead starts ## Actual Behavior Fails to start due to missing write permissions. ## Steps to Reproduce the Problem 1. Set-up a server-profile as root, add `local_users: true` and a valid usrsources.ini but use the default `user_group: 999:999` setting 2. Start linkahead 3. Set `user_group: 0:0` and verify that this solves the problem ## Specifications - Version: LinkAhead 0.15.0 - Platform: Ubuntu 22.04 ## Possible fixes Retrace the old and the new chown commands when building the image. Did we miss one? ## Workaround Start with `user_group` matching the user that is running the LinkAhead service (0:0, i.e. root in this case)