I assume that at some points in the execution, the client (where the task is running) is sending JSONs to the mongo service, and that is what we see in the web UI.
Since we are talking about a case where there is no internet available, maybe these could be dumped into files/stdout and let the user manually insert them.
The manual insertion UX could be something like a CLI copy-paste or and endpoint for files - but since your UX is so good ( 🙂 ) I'm sure you'll figure this part out better

In standard docker TimelyPenguin76 this quoting you mentioned is wrong, since the whole argument is being passed - hence the double tricky quotation I posted above

I'm using pipe.start_locally so I imagine I don't have to .wait() right?

But does it disable the agent? or will the tasks still wait for the agent to dequeue?

I'm not, just want to be very precise an consice about them when I do ask... but bear with me, its coming 🙂

But I'm naive enough to believe that 10.2 is compatible with 10.1 as it is a minor upgrade

Lets see if this is really the issue

but remember, it didnt work also with the default one (nvidia/cuda)

Let's try

🤞