[
https://issues.apache.org/jira/browse/AIRFLOW-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765144#comment-16765144
]
Merouane Benthameur commented on AIRFLOW-3063:
----------------------------------------------
I have worked on a custom Docker Operator for airflow, because at my work we
wanted to use volume_form in the container. so I have refactored the docker
operator to accept all possible arguments in docker-py lib dynamically.
I would love the share the work I've done.
> Support all docker options to create containers with DockerOperator
> -------------------------------------------------------------------
>
> Key: AIRFLOW-3063
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3063
> Project: Apache Airflow
> Issue Type: Bug
> Components: docker
> Affects Versions: 1.10.0
> Reporter: Victor
> Priority: Major
>
> The original need is to run a container in a predefined docker network, but I
> suppose the operator should support setting any of the options supported by
> the docker-py API.
> What is not totally clear is if it should be possible to define any of the
> options that can be passed to the docker API in a templated fashion or not.
> In my case, a temporary network could for example have been created in a
> previous operator and pushed to xcom.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
