#3833 [BUG] pyflyte run fails when ContainerTask is executed locally Issue created by zeryx Describe the bug When using pyflyte run on a workflow that contains a ContainerTask, the ContainerTask and WF fails during tracing when attempting to run locally. When either passing

--remote

or registering a workflow with pyflyte register to a flyte cluster, no error is reported.

TypeError: Error encountered while executing 'proxy_registration_wf':                            
                                      Failed to convert outputs of task 'register' at position output:                               
                                      Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple:                      
                                    STRING>                                                                                          
Failed with Unknown Exception <class 'TypeError'> Reason: Error encountered while executing 'proxy_registration_wf':
  Failed to convert outputs of task 'register' at position output:
  Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple: STRING>
Error encountered while executing 'proxy_registration_wf':
  Failed to convert outputs of task 'register' at position output:
  Python value cannot be None, expected <class 'str'>/<FlyteLiteral simple: STRING>

Expected behavior either throw an error stating that ContainerTasks are not supported with local pyflyte run execution, or provide support for executing ContainerTasks locally. Additional context to reproduce https://gist.github.com/zeryx/b3d4cca7594de252a08ae8a02c2d5d6b create a WF (or dynamic task) that triggers a ContainerTask define the ContainerTask to have inputs and outputs execute an arbitrary step within the ContainerTask (not reading or writing from pipes) trigger the workflow with

pyflyte run

without

--remote

Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte