Transcoder fails when `/transcode` is on a network share
Update: This has been resolved in 1.5.4 which is available to the public. Removing the announce status on this topic.
Starting with 1.5.1, if the transcoder is working with either the AC3 (Dolby Digital), EAC3 (Dolby Digital+), or TrueHD, then the process can fail if the
/transcode is really located on a network share. The transcoder requires certain filesystem capabilities to work which are typically not available on shares.
This is most relevant for FreeNAS Corral users because any volumes you create are network shares. If you examine your docker config and find that
/transcode is located on the host, such as seen below, then you need to change this:
The easiest solution is to delete the volume and then it will persist in the VM. Check the checkbox next to the volume and then hit the trash button. Finally save the container.
After this you will see the
/transcode mount existing, but it will be in the VM instead.
Lastly, since FreeNAS does NOT recreate the container correctly when you edit it, it completely bypasses the initial setup scripts that run in the container the first time. One of these steps is to correct the permissions of the
/transcode directory. So click on the
Console button for your container and in the new browser window type
chown -R plex:plex /transcode.