Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

hello - i'm working on a `ContainerTask` and would like to be able to dynamically pass in an image ref. i can use `{{.image.reasoning.fqn}}:{{.image.reasoning.version}}` but i expected `{{.inputs.reasoning_image}}` to work as well. however, i found that `inputs=kwtypes(inputfile=FlyteFile, reasoning_image=str)` is not used when trying to resolve the `image` reference.

is that intentional? it seems like populating `.image` is more restrictive than `.inputs`, so maybe there is a safety concern here?

sorry, that's specific to my container task

the above works if i pass in `--image reasoning=myimage:v` to `pyflyte run` or if i set config with:
```images:
  reasoning: myimage:v```

but that isn't quite as flexible as using containertask inputs

hmm, currently the image cannot be changed at runtime