This message was deleted.
# flyte-support
u
This message was deleted.
a
I think FlyteDirectory is supported as an output of ContainerTask but not as an input (there's work in progress)
not sure if it explains the behavior you see
s
the subsequent task is a regular task not container task. The container task copies the output to flyte backend storage in s3 but it somehow returns a single blob instead of multipart blob