I think it should be considered why the tunnel requires the tunnel name to be set when it already has the tunnel ID. It seems there is something in the chart or container that is misconfigured, as the error thrown when the tunnel name is not set is in contradiction with the case:

"cloudflared tunnel run" requires the ID or name of the tunnel to run as the last command line argument or in the configuration file.

Right now, it should be:

"cloudflared tunnel run" requires the ID and name of the tunnel to run as the last command line argument or in the configuration file.

to align with the behaviour of the helm chart.

I am not familiar with the setup of the cloudflare-remote-tunnel, so I hope someone else can jump in with a quick bit of docs on how to get that rolling.