How can I access the storage of apps?
I have heavy_script installed, but when I try to mount the storage of an app (for example, transmission), I get an error message that the app doesn’t have a PVC
Are you still using TrueCharts? Heavyscript is only for those.
What version of Scale are you using?
TrueNAS-SCALE-23.10.2
I’m waiting to get all my apps in order (migrating from TrueCharts) before updating the Scale version
I’m migrating out of truechars
What is the tool for truenas apps? (using the UI shell to access the storage is very unconvenient)
There is a file manager app that might be helpful. No experience with that.
Also forget the UI shell - use SSH. It’s the only way if you want to continue to use a Unix based appliance.
For TrueNAS SCALE apps you can define host paths for all volumes so the data is already outside the container. Then share these or use SSH.
How do I ssh into an app?
You don’t. The app storage is either a volume mapped to a host path so you know where it is or it is in /mnt/.ix-apps/… somewhere. Just cd into the proper directory.
I meant use SSH for TrueNAS, not the web UI shell,
Applies to EE and up.
I see. thanks.
So, if I understand correctly, it is not available for the current version
Is it safe to upgrade to EE (24.x) when some of my apps are still truechart apps?
EE is the current version.
It’s safe but you won’t have the apps 
TrueCharts is dead. Has been since August 2024 (for TrueNAS).
So, I’ll save the settings of all relevant apps
On this note, when I migrated transmission I ran into an odd problem:
I set a mount point of /downloads to my torrents dataset so that completed downloads are accessible by other apps
The /downloads directory is the default directory for storing data, and is created as part of the app
In my truecharts version this worked perfectly, and the mount overridden the local directory. However, in my truenas version, the local directory “trumps the mount”
If I mount my dataset on another location, the mount succeeds
What is the recommended way:
- delete the local
/downloadsdirectory, to create a new mount point? (risking that the problem will return when the app is updated) - change the transmission setting to point to a mount point on another directory (seems more reasonable…)
Not familiar with transmission but the general idea is to provide one host path per volume for all data the app template allows you to put in a separate volume.
So I started deploying transmission and I get a dialog with these volumes for “Storage Configuration”:
- Transmission Config Storage
- Transmission Completed Downloads Storage
- Incomplete Dir Storage
The last one looks a bit inconsistent to me, because further down it refers to “Completed Download Storage” again, but with “/downloads/incomplete” as the mount point inside the container. But that might be me running Fangtooth, already and a bug in the new UI. Or a minor bug in the app template.
Anyway you are supposed to create a bunch of datasets to your personal liking for these. I have a top level one named “data”. If I ever redo it I would probably change that to “apps”. Whatever. And then, what I would do is:
- mypool/apps/transmission
- mypool/apps/transmission/config (*)
- mypool/apps/transmission/downloads
- mypool/apps/transmission/downloads/completed (*)
- mypool/apps/transmision/downloads/incomplete (*)
The datasets without (*) get the share type set to “Generic” and the datasets with (*) to “Apps”. Generally leaves are set to “Apps”.
Then go back to the app deployment and change every ixVolume storage to Host Path and map your newly created datasets to the mountpoints inside the container.
HTH,
Patrick
P.S. Looks the same in EE, so there is a minor inconsitency in the app “recipe”. You will probably figure it out. Every volume defined in the menu should go to an individual “Host Path” mapped to a newly created dataset.
2 Likes
Looks like one confusing header label to me. Should be a simple fix in the catalog.
FYI since the apps catalog maintenance is independent from TrueNAS versions, anything you see in an app configuration form should be the same in EE or FT (or GE, etc.).
1 Like