hi! i have a problem whit some apps. In this case it is homepage.
I install the app on ix volume and all works fine. But i cant edit anything so it does not work for me.
When i install it on a hostpath, i get an error on the logs: “error copying config Error: EACCES: permission denied, copyfile ‘/app/src/skeleton/settings.yaml’ → ‘/app/config/settings.yaml’”.
the description on the app says that it runs as root, so, the hostpath is set to root as owner and root has full control.
this happend to me whit other apps like homer, dashy… i am getting crazy … any ideas?
sorry but i am too noob here. user and permissions on that dataset:
apps: full control
group builtin_users: full control
root: full control
new user whit id 1000 as LarsR said: full control
still not working. i am sure u all have reason and it is a problem whit permissions but i dont get the key on this
I would expect that should work, but it might have something to do with how you set the ACL permissions.
But I have been able to install Homepage twice now simply by doing this.
Create a dataset for Homepage. I have tried this with both Apps and Generic presets, POSIX and NFSv4 ACLs. You can leave dataset ownership at defaults for root or your admin user.
Install Homepage. In the Storage Configuration, select Host Path. Select Enable ACL. Select the path to your new dataset. Click Add next to ACL Entries and add a FULL_Controll entry for UID 1000 (this can be an entirely container-side user, there doesn’t even need to be a UID 1000 on TrueNAS as long as you add the ACL entry here). Finish configuring and click Save to deploy.
Well i am not sure why, but It works, the homepage app IS working, BUT, the dataset IS empty, y try to share It on filebrowser, even on a smb share, but It IS empty, there sould be the file to configure It? Or i have to create them?
My understanding is the details screen for the app has a Run-As widget that lists the UIDs for the app.
After referring to this, next you can edit your app and enable ACL, select the host path to the dataset, add an ACE entry for the user, enter the run-as UID and assign it full control permissions.
Repeat for each dataset/storage volume.
This should fix the problem.
You can also edit the ACL permission starting on the Datasets screen. Select the row for the dataset, click Edit on the Permissions widget to open the Edit ACL screen. Add ACL entries for the users.
You might have to go the Credentials > Users screen, click the option to show builtin-users, scroll down to the UID for the run-as users listed in the Apps details screen widget to get the user name to enter in the Edit ACL screen.