path mapping in transmission docker

Hello all,

I just upgraded from OMV4 to OMV5. Since there is no transmission extension in OMV5 anymore I used docker. Working ok so far. I have one problem though:

I am using remote GUI on all the various machines in the house to control transmission. One very handy feature is path mapping. That enables you to just click on a download in the GUI and it opens the folder it is in. It is necessary to translate the internal path that transmission sees to the equivalent path that the client sees, like so:

That does not work anymore if transmission is running inside docker. What can I do?

I can answer my own question, and maybe that shows I am slowly getting a feel for how docker works:

the path mapping from omv5 (the /srv/dev-disk-by...) to the folder that transmission thinks it is operating in is done by docker. So you only need to put in the download folder as transmission sees it. You can find it here:

then put that in the path mapping tab and your done: