brief-family-9488
05/27/2025, 10:44 PMjolly-florist-66728
05/27/2025, 10:44 PMcontainer_image
parameter in the @task
decorator and then using the FlyteRemote Python API or the pyflyte register
CLI. The custom image can be defined via an ImageSpec
object, and FlyteRemote allows you to register workflows and tasks programmatically, including passing an image configuration if needed. For example, you can use remote.register_workflow()
and provide the appropriate image configuration for your tasks that require a custom image. See the ImageSpec documentation and FlyteRemote usage for details.
If you want to use the CLI, you can also pass the --image
flag to pyflyte register
to specify the custom image at registration time, which avoids hardcoding the image in your code and supports CI/CD workflows. See Registering workflows for more information.
Would you like more detail or a code example?
Sources:
- ImageSpec documentation
- Registering workflows 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.brief-family-9488
05/27/2025, 10:59 PMjolly-florist-66728
05/27/2025, 10:59 PMcontainer_image
parameter in the @task
decorator or by providing an image configuration (such as an ImageConfig
or ImageSpec
) in the SerializationSettings
passed to register_workflow
. See the FlyteRemote registration example for details.
However, the data sources do not provide a full, explicit code example for using FlyteRemote with a custom image, but they confirm that it is possible by passing an image configuration to the registration call.
Would you like more detail or a step-by-step code example?
Sources:
- FlyteRemote registration example 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.