How to install truetool or heavyscripts, need root access/rights

[KristofferLindberg]

Im trying to get into the pods to do some reconfiguring. As far as I have understood I can do that by using truetool or heavyscripts. Only problem is that when I try to install it I get an access error, seems I dont have the correct rights with the admin account. Have I misunderstood something or? I have upgraded to 2022.12.1 and admin is member of builtin_admininstrqators

 

[MisterE2002]

Not sure if i understand. But are you trying to change something in a running container instance? You know that everything will be wiped at the next run (except if you want to change a setting which is stored on the host (PVC or host path mapping) but usually you can/should use the app's GUI.

 

[LarsR]

are you using "sudo" in front of the commands?
I'm using truetool inside an ssh session with my own user and have to add sudo to the commands.

 

[KristofferLindberg]

Ok, but in that case, how do i change for instance different settings in nextcloud app which isnt available through the truecharts gui? Regarding the root access, i cant for instance execute git clone https://github.com/truecharts/truetool.git. Dont have the correct rights for this. I have ssh session and after login in su admin, so im logged in as the admin user

 

[MisterE2002]

Settings are stored in PVC or HostPath. You should not modify "OS Things" in a container. (install packages, etc.) This will be wiped the next run.
Not familiar with your scripts/tools. But i use the Truenas web GUI. I select the app -> hamburger menu -> Shell access.

You will become the user (you configured the application to run as). If the App is designed correctly you should have the permissions to modify the app settings. Usually stored in /config.

 

[MisterE2002]

re-reading your question. It seems you are installing something on the truenas host itself. As i am not familiar with those scripts i can not really help. But i know iX is busy with root -> admin changes so it is possible something broke.
Who created those scripts and what do they say about "admin" usage instead of "root"?

 

[LarsR]

The script is from a user from the forums called heavybulls and truecharts adapted that script in their own ways and calls it truetool.
You can save it on your system, and execute it and do things like mounting pvc storage to edit the files inside it, app catalogue sync and bulk upgrade of apps.
I'm using it with my own user who is a member of the buildin administrators and only have to add sudo to the command so it runs.

Edit: for more information see https://github.com/truecharts/truetool

 

[KristofferLindberg]

The script is from a user from the forums called heavybulls and truecharts adapted that script in their own ways and calls it truetool.
You can save it on your system, and execute it and do things like mounting pvc storage to edit the files inside it, app catalogue sync and bulk upgrade of apps.
I'm using it with my own user who is a member of the buildin administrators and only have to add sudo to the command so it runs.

Edit: for more information see https://github.com/truecharts/truetool

The problem for me is that I have installed truenas scale with the admin as recommended instead of root. When i try to run the command
sudo git clone https://github.com/truecharts/truetool.git i get the following error:

[sudo] password for admin:
Cloning into 'truetool'...
error: chmod on /mnt/tank/data/scripts/truetool/.git/config.lock failed: Operation not permitted
fatal: could not set 'core.filemode' to 'false'

guess it has something to do with premissions or?

If i try to run sudo curl -s https://raw.githubusercontent.com/truecharts/truetool/main/bootstrap | bash it says "This is intended to be ran as root"
However I dont have the root account, only admin which is member of builtin_administrators

 

[danb35]

guess it has something to do with premissions or?

It probably has to do with the location that you're using being a shared directory, and thus using ACLs rather than standard Unix permissions.

 

[KristofferLindberg]

It probably has to do with the location that you're using being a shared directory, and thus using ACLs rather than standard Unix permissions.

Found a way around it now. Added admin to root group and then it was possible to run the command with sudo.