When creating a an application, its very simple to use the ix-volume option, where the system will create a system managed dataset and export for the application.
It can be very challenging for a user to extract their data from the IX-Volume if they later decide that they would like to have the data easily available on their pool for replication, snapshots or migration purposes.
In order to resolve this it would be very useful if there were a “convert to host path” type option for IX-Volumes.
This button/option would simply allow the user to select a dataset, and then it could zfs rename the dataset to this location, and update the application settings,
thus converting the ix-volume to a user managed Host Path.
I imagine this could be accomplished with a button next to an already created ix-volume on the edit app page.
I’ve only just learned that ixVolumes were never intended to hold any important user data. So looking at my apps, there are several places that ixvolumes were used and should be host paths.
While waiting for this request to be accepted or not I’m wondering if there are any scripts that might achieve the same thing, so I don’t need to recreate the entire app to change one path.
I have recently had to re-setup apps for just this reason, I wanted to stop using ixVolumes and use HostPath for easier access to app related files. A lot of time could have been saved if there was the ability to convert/move. I have reached my vote limit but I would like to see this feature request considered.
+1 to the idea. All my apps failed 2 start and were reinstalled manually by copy-pasting all parameters and directories after migration to EEL. I was trying to have all data separated ffrom ix-volime to have them on hdd pool (remembering about SSD TBW parameter), and made custom dirs during installation. After migration all custom volumes were threated as ix-apps. All started after long copy-pasing, no data loss, but reminding this, hmm… w\o pleasure.
Any news about this?
This should not just allow changing to host path but also to tmpfs.
For example Frigate by default uses ixVolume for everything. But I just discovered that Frigate Cache Storage is actually recommended to be on tmpfs. But I cant change this once its already installed.
TrueNAS should allow you to change after deployment, but also being containers you can just destroy the app and redeploy with non-ix volumes and tmpfs.
The whole issue of ix-volumes not being intended for production use is bizarre. It is not hard to create datasets with automation, and if ix-volumes are not intended for production use then they should not be an option. TrueNAS could just as easily and with less confusion and opportunity for error (e.g. not configuring snapshots on the hidden ix-apps dataset) have a default apps dataset provided by the user (and that can be overridden) with datasets created there instead.
Great news! This feature request has gathered enough community interest to be transferred to our internal roadmap for detailed scoping and assessment.
What this means:
Our product team will now evaluate technical feasibility, resource requirements, and alignment with our product strategy
This request is now closed for voting, and your votes have been released back to use on other requests
We’ll conduct a thorough analysis to determine if and how this feature might be implemented
Please note that transfer to the roadmap doesn’t guarantee implementation - some features may not proceed based on our assessment findings, however we will update this thread once a decision has been made.
Thank you to everyone who voted and contributed to the discussion. Your input has been invaluable in helping us understand the community’s needs and use cases for this feature.
