That sounds like a sequencing issue. If one container has a template function that references another (for instance, with the NodePrivateIPAddress function) then that container must start after the one it references - otherwise the value won’t have been populated yet. This can be enforced with subscriptions - Marc’s written up how to use them here.
I don’t think that line (as currently written) will ever produce useful output, as it is evaluated before any components are scheduled - and there’s no way to sequence it to run after components are scheduled.