Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A2094200D01 for ; Fri, 22 Sep 2017 21:55:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A09631609D0; Fri, 22 Sep 2017 19:55:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E7B9D1609BE for ; Fri, 22 Sep 2017 21:55:04 +0200 (CEST) Received: (qmail 37510 invoked by uid 500); 22 Sep 2017 19:55:04 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 37496 invoked by uid 99); 22 Sep 2017 19:55:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Sep 2017 19:55:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 97112191F38 for ; Fri, 22 Sep 2017 19:55:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6UKgQKWyAltH for ; Fri, 22 Sep 2017 19:55:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5EBF56127A for ; Fri, 22 Sep 2017 19:55:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C0387E0A04 for ; Fri, 22 Sep 2017 19:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5CD3824242 for ; Fri, 22 Sep 2017 19:55:00 +0000 (UTC) Date: Fri, 22 Sep 2017 19:55:00 +0000 (UTC) From: "Gregory Benison (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AIRFLOW-1633) docker_operator needs a way to set shm_size MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 22 Sep 2017 19:55:05 -0000 Gregory Benison created AIRFLOW-1633: ---------------------------------------- Summary: docker_operator needs a way to set shm_size Key: AIRFLOW-1633 URL: https://issues.apache.org/jira/browse/AIRFLOW-1633 Project: Apache Airflow Issue Type: Improvement Reporter: Gregory Benison The "docker run" command line client has an option "--shm-size" that allows setting the size of /dev/shm in the container. The "docker" package - on which docker_operator is based - does provide an interface for setting this property; docker.utils.create_host_config() has a "shm_size" argument that defaults to None. However docker_operator calls that method in a way that does not provide a mechanism for accessing that argument: {noformat} self.container = self.cli.create_container( command=self.get_command(), cpu_shares=cpu_shares, environment=self.environment, host_config=self.cli.create_host_config(binds=self.volumes, network_mode=self.network_mode), image=image, mem_limit=self.mem_limit, user=self.user ) {noformat} It would be useful to provide a way to pass the "shm_size" option to the call to create_host_config(). Actually create_host_config() has a large number of options that can't be controlled through docker_operator - perhaps it would make sense to find a way to expose all or most of them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)