Pre-built Container Task Plugin#

A pre-built container task plugin runs a pre-built container. The following are the advantages of using a pre-built container in comparison to a user-defined container:

  • Shifts the burden of writing Dockerfile from the user who uses the task in workflows to the author of the task type.

  • Allows the author to optimize the image that the task runs on.

  • Makes it possible to (largely) extend the Flyte task execution behavior without using the backend GOlang plugin. The caveat is that these tasks can’t access the K8s cluster, so you’ll still need a backend plugin if you want a custom task type that generates CRD.


Take a look at the example PR, where we switched the built-in SQLite3 task from the old (user-container) to the new style of writing tasks.

There aren’t many changes from the user’s standpoint: - Install whichever Python library has the task type definition (in the case of SQLite3, it’s bundled in Flytekit, but this isn’t always the case

(for example, SQLAlchemy)).

  • Import and instantiate the task as you would for any other type of non-function-based task.

How to Write a Task#

Writing a pre-built container task consists of three steps:

  1. Defining a Task class

  2. Defining an Executor class

  3. Creating a Dockerfile that is executed when any user runs your task. It’ll most likely include Flytekit, Python, and your task extension code.

To follow along, use the PR (mentioned above) where we migrate the SQLite3 task.

Python Library#


New tasks of this type must be created as a subclass of the PythonCustomizedContainerTask class.

Specifically, you need to customize the following three arguments which would be sent to the parent class constructor:

  • container_image: This is the container image that will run on a Flyte platform when the user invokes the job.

  • executor_type: This should be the Python class that inherits the ShimTaskExecutor.

  • task_type: All types have a task type. Flyte engine uses this string to identify which plugin to use when running a task.

The container plugin will be used for everything that doesn’t have an explicit match (which is correct in this case). So you may call it whatever you want, just not something that’s already been claimed (like “spark”).

Referring to the SQLite3 example,


Note that the container is special in this case since we utilize the Flytekit image.

Furthermore, you need to override the get_custom function to include all the information the executor will need to run.

Keep in mind that the task’s execution behavior is entirely defined by the task’s serialized form (that is, the serialized TaskTemplate). This function stores and inserts the data into the template’s custom field. However, keep the task template’s overall size to a minimum.


You must subclass and override the execute_from_model function for the ShimTaskExecutor abstract class. This function will be invoked in both local workflow execution and platform-run-time execution, and will include all of the business logic of your task.

The signature of this execute function differs from the execute functions of most other tasks since the TaskTemplate determines all the business logic, including how the task is run.


This is the custom image that you specified in the subclass PythonCustomizedContainerTask. Out of the box, when Flyte runs the container, these tasks will run a command that looks like this

pyflyte-execute --inputs s3://inputs.pb --output-prefix s3://outputs --raw-output-data-prefix s3://user-data --resolver flytekit.core.python_customized_container_task.default_task_template_resolver -- {{.taskTemplatePath}}

This means that your Docker image will need Python and Flytekit installed. The container’s Python interpreter should be able to find your custom executor class at the import path

The key takeaways of a pre-built container task plugin are:

  • The task object serialized at compile time does not exist at run time.

  • There is no user function at platform run time, and the executor is responsible for producing outputs based on the task’s inputs.

Total running time of the script: ( 0 minutes 0.000 seconds)

Gallery generated by Sphinx-Gallery