I’m not sure about docker, but on regular install you need to type the chown command from your user shell, not from the librenms user shell, ie. if the shell says librenms@<hostname> type exit which will bring you out to <your user>@<hostname> shell where you presumably used sudo su - librenms to enter the librenms shell in the 1st place.
Then you can use the command and when sudo prompts you for password it’s your user’s password, not password of user librenms. On most modern installations the default user is in sudoers, however the librenms user we add when installing librenms is not. Perhaps in your case you could add librenms user to sudoers and grant it permission to execute setfacl without password?.
(corrected)
If you are already in the librenms user, do whatever necessary to end up in ‘root’ user and after, just type :
root@myServer# chown -R librenms:librenms /opt/librenms
The chown command needs to do something with the directory /opt/. This doesn’t exist in the file system of the Synology host; /opt/ only exists within the Docker container, so I am afraid I had to log in to the Docker container first(?)
I have no clue about docker part, but my previous answer was not good
What user do you end up in when you docker exec ? if it is root, then you can run the chown. If not, you need to be root to run it. Previous issue was that you cannot run ‘sudo’ from librenms user, but not doing sudo means you need to be root first That’s what I did not explain correctly in the previous post:)
SSH into my Synology.
docker exec -it librenms bash
chown -R librenms:librenms /opt/librenms
And if the path of the librenms homedir is not /opt/librenms, then yes, you have to correct it to your real librenms homedir.