Migrating docker containers, can't mount NFS directly

I have an *arr stack that I am trying to migrate from a Linux host into Truenas as custom apps.

The containers on the Linux host are all configured to use the host network and mount the NFS shares directly into the containers via their docker compose configs.

However, when I try to create custom apps on Truenas, there’s no option in the storage area of the GUI to specify NFS mounts. Is there a way for me to add these via the cli?

I would like to do this for two reasons.
1: all the *arr apps and the Emby server they feed need to mount the shares via the same full path
2: trying to use host path mounting is resulting in a lot of complexity regarding permissions on my media volume and I can’t figure out a way to make the containers create files that result in the same effective permissions as if they were created via the NFS mount.

Does all your storage live on your Scale server? If so, why not just use binds to the local storage?

The storage lives on scale.

Emby lives on a separate server and mounts the NFS share. The share is global r/w for any connected device which is restricted by IP and all connections r/w as the same user.

When I try to use host mapping they try to r/w to the folder as the account running the container, not the user that the NFS export is configured for. Repermissioning my media shares isn’t something I really want to do, but it’s something I might HAVE to do if there’s no way to get the containers to mount an externally hosted share. Also, I will need to re-home the containers to a new instance eventually, and being able to migrate the data separate from the container itself would be nice.