Just worth maybe updating the doco/calling out that if the user is 'mounting' in the config file from the Docker host, they'll have to ensure the permissions are correct on the config file.
Fixed this by making the config file owned by 2000:2000 then I can still restrict the reading of the config file on the Docker host while allowing the container to be able to read the file.
Just noticed my solariot image has been crashing in a loop since the introduction of the custom user in the dockerfile:
Just worth maybe updating the doco/calling out that if the user is 'mounting' in the config file from the Docker host, they'll have to ensure the permissions are correct on the config file.