Given that the flash drive can't be encrypted and that docker user-templates definitions often containing credentials and keys are stored in the clear, it would be nice to have an option to move /boot/config/plugins/dockerMan on a pool drive (cache).

 

Could be as simple as storing data on an unpublished share and making a symlink to the original folder.

 

I tried, but it won't let me do "ln -s /mnt/cache/dockerMan /boot/config/plugins/dockerMan".

 

Might be a cool approach for any other "config" that doesn't need to be available before the array is started and available.

You could move the key variables from the template to an envfile, and locate that file somewhere secure and encrypted (I usually go with appdata path).
This way the container templates in flash drive would be always sanitised.

To enable this, edit the template and adding this to your Extra Parameters field (toggle advanced view in top right):
--env-file=/mnt/cache/appdata/homepage/.env
edit path to where you prefer, this is an example for homepage env file path.

env file itself is fairly simple, in the form VARIABLE=VALUE

USERNAME=johndoe
API_KEY='HelloWorld1234'
DATABASE_URL="http://localhost:5432"

It's what I did ! But still, there are some parameters that can't be in an ENV FILE, like Post Arguments that MIGHT contain sensitive data.

Needs a proper secrets system like Komodo Core.