Persistent Storage for Apps built via Docker Launcher

[PatrickStuartMoney]

Is it possible to enable persistent storage on apps built via Docker Launcher on SCALE?

I did an initial test with a Sonarr app and uploaded my backup from my CORE installation, on rebooting the app all data is lost.

 

[Kuro Houou]

Did you happen to figure this out? trying to launch a custom container for Scyrpted as well but whenever it gets restarted all the data goes with it :( Needs to be a checkbox to persist storage or something?? Am I missing that?

 

[HoneyBadger]

In the "Launch Docker Image" window, you should be able to set up a host path under the Storage menu and map it into the pod.

You'll need to point the Host Path value to an existing dataset, and the Mount Path will be the directory inside your pod, such as /var/MyData

For Sonarr specifically, this is now available in the TrueNAS SCALE Community repository as well!

 

[Kuro Houou]

In the "Launch Docker Image" window, you should be able to set up a host path under the Storage menu and map it into the pod.

View attachment 66378

You'll need to point the Host Path value to an existing dataset, and the Mount Path will be the directory inside your pod, such as /var/MyData

For Sonarr specifically, this is now available in the TrueNAS SCALE Community repository as well!

Do you know if its better to use the Host Path Volume or the other one below named Volumes? I found the path to the config data for Scrypted. Just wanted to make sure I use the right storage type?

 

[HoneyBadger]

Do you know if its better to use the Host Path Volume or the other one below named Volumes? I found the path to the config data for Scrypted. Just wanted to make sure I use the right storage type?

Volumes are stored under the /ix-applications/docker/volumes or /ix-applications/releases/appname/volumes/ix_volumes path in the pool you assign for holding apps, so if you're using small SSDs for this dataset for speed, then you might not want to put large amounts of data there. A config file or small application database would be fine; I wouldn't put something like a media server's metadata there though (or a temp directory for transcoding large files)

Volumes also currently get pruned if you delete the associated application, but Host Path doesn't.

The Docker documentation has some other comparisons between Volumes and Host Path as well that might be relevant - note that the TrueNAS SCALE implementation might differ slightly though.

Storage

Overview of persisting data in containers

docs.docker.com

 

[Kuro Houou]

Thanks for that clarification, I will use the Host Path Volume instead for this use case, even though the DB will be small, I want it to persist even if the app/container goes away.

 

[hugo99]

hi
i did as described (influxdb, docker image). hostpath leads to an existing dataset. but stilll nothing is saved in there, the directory is empty. any ideas how i can put my databases onto an existing dataset?