The docker image to be used if the repository does not specify one.
Name of the network to which to connect the launched container at creation time
Information for using a non local/public docker registry
The list of environment variables names to include in the docker container. Each can be of the form KEY=VALUE or just KEY (in which case the value will be pulled from the local environment)
key-value pairs that can be passed into containers.create. See https://docker-py.readthedocs.io/en/stable/containers.html for the full list of available options.
Names of the networks to which to connect the launched container at creation time
Launches runs in a Docker container.
The docker image to be used if the repository does not specify one.
Name of the network to which to connect the launched container at creation time
Information for using a non local/public docker registry
The list of environment variables names to include in the docker container. Each can be of the form KEY=VALUE or just KEY (in which case the value will be pulled from the local environment)
key-value pairs that can be passed into containers.create. See https://docker-py.readthedocs.io/en/stable/containers.html for the full list of available options.
Names of the networks to which to connect the launched container at creation time
Whether retries are enabled or not. By default, retries are enabled.
{
"enabled": {}
}
{}
{}
Executor which launches steps as Docker containers.
To use the docker_executor, set it as the executor_def when defining a job:
from dagster import job
from dagster_docker import docker_executor
@job(executor_def=docker_executor)
def docker_job():
pass
Then you can configure the executor with run config as follows:
execution:
config:
registry: ...
network: ...
networks: ...
container_kwargs: ...
If you’re using the DockerRunLauncher, configuration set on the containers created by the run launcher will also be set on the containers that are created for each step.