You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/21 15:43:00 UTC

[jira] [Commented] (AIRFLOW-3063) Support all docker options to create containers with DockerOperator

    [ https://issues.apache.org/jira/browse/AIRFLOW-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869597#comment-16869597 ] 

ASF GitHub Bot commented on AIRFLOW-3063:
-----------------------------------------

ashb commented on pull request #5049: [AIRFLOW-3063] - Make DockerOperator support all docker arguments
URL: https://github.com/apache/airflow/pull/5049
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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: operators
>    Affects Versions: 1.10.0
>            Reporter: Victor
>            Priority: Major
>              Labels: docker
>
> 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)