Hello,

Currently unraid can only mount volumes with docker eg:

docker run -v '/mnt/user/appdata/unifi-controller-reborn/':'/unifi/run':'rw'

However I need to be able to mount tempfs eg:

docker run --mount type=tmpfs,dst=<mount-path>

from: https://docs.docker.com/engine/storage/tmpfs/#syntax

The inability for unraid to be unable to do this means that files that do not need to persist must now be stored on the array which can be undesirable, and complicates security of read only images. This was discussed in github issue here: https://github.com/11notes/docker-unifi/issues/33

Proposal: Add gui method to create tempfs mounts as per dockers documentation so that both GUI and community apps XML can support this method. This would allow me to take advantage of this feature and no longer store unneeded files in the docker appdata area.

Kind regards

P

its already possible, you just put it in extra parameter (toggle the advanced view)

4 hours ago, Mainfrezzer said:

its already possible, you just put it in extra parameter (toggle the advanced view)

Hi there,

This actually does work, and I have got it working this way, but is this in line with unraid mentality? You could simply remove all parts of the gui and leave only "extra parameters" and expect everyone to simply add every single switch, volumes, any ports and so on via this single line. I feel there is a case for the GUI having common settings exposed otherwise why have any settings exposed at all no?

However this does resolve my immediate problem so will use this method for now.

Kind regards

P

Edited December 16, 2025Dec 16 by PeteAsking

my understanding is yes as the template just builds a docker run line. and anything that can be setup in a docker run line and be placed there. This includes and is not limited to other advance docker option that affect making a ram disk and zdisk for dockers applications.

I've done similar with pbs and plex for transcode using extra par lines making ram disk of variant sizes. and temp fs to be deleted upon reboot. Included attempts to get unifi protect running under a docker using these mount and temp option in extra parameters.

some of my template even ship with some extra options so yes To my understanding as I have not gotten a no or a change, yes this lines up with expected expatiation and use case in templates and how unraid intended to run...

more info in the docker docs:
https://docs.docker.com/engine/storage/tmpfs/

there also the make the tempfs in the extra parm and path mount it in the unraid template where you can specify readonly...



including using bind mounts...