supersnellehenk
commented
3 days ago The Tdarr container image has a Tdarr_Node built in, which gets enabled using the internalNode=true environment variable. Using this setup, you don't need a separate Tdarr_Node container.
If you want to use a different machine using Docker as a node, all they'd need is the Tdarr_Node container.
Bare metal installs without Docker don't have this, they'd have to start both the Tdarr_Server and Tdarr_Node executables.
Altheran88
In the docker documentation, here : https://docs.tdarr.io/docs/installation/docker/run-compose It specifies :
The 'tdarr' container contains Tdarr_Server and a Tdarr_Node Set internalNode=true to enable the Node in the Server container. Where setting internalNode=true/false enables or disables the Tdarr Node running in the Server container.
There is also "-e "internalNode=true" \ -e "nodeName=MyInternalNode" \" in the compose example. And all the transcoding settings + access to the GPU for the transcoding.
In the getting started page here https://docs.tdarr.io/docs/installation/getting-started it says : You can run Tdarr using only a single machine. Using extra Tdarr Nodes on multiple machines to increase transcoding resources is optional.
But in the table just bellow, it says : Server | The core of Tdarr. All modules connect with it. Does not do any encoding. As of v2.00.08 it contains Tdarr_WebUI.
Then : To run Tdarr, you'll need the Server and a Node (one or multiple).
It seems indeed that there are no more internal node as I no longer see a node inside my Tdarr container.
So, which is it ? Can we run only the Tdarr container ? Or do we need the Tdarr _Node container also ?
If Tdarr_Node is required, and Tdarr no longer transcodes, can the Docker compose be cleaned up so it doesn't include the settings to give access to transcoding resources ?
Thank you !