Summary
The user is experiencing difficulties with propagating FlyteUserException from a ContainerTask to a Flyte workflow, noting that it functions correctly with decorated tasks but fails in a Raw-Container, leading to a non-zero exit code despite exceptions being logged. They have checked container logs and attempted to re-raise exceptions, but their overridden execute method in ContainerTask is not being invoked. The user is seeking guidance on the appropriateness of overriding execute and the reasons for their implementation's failure. They also ask about writing out LiteralMap in relation to the ContainerTask execute method and suggest that handling user-provided errors in raw containers could be enhanced by modifying flytecopilot, although this has not yet been done.