Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4511518986 for ; Wed, 17 Jun 2015 05:10:53 +0000 (UTC) Received: (qmail 74179 invoked by uid 500); 17 Jun 2015 05:10:53 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 74127 invoked by uid 500); 17 Jun 2015 05:10:53 -0000 Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list dev@aurora.apache.org Received: (qmail 74116 invoked by uid 99); 17 Jun 2015 05:10:53 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 05:10:53 +0000 Received: from mail-oi0-f54.google.com (mail-oi0-f54.google.com [209.85.218.54]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C7CDB1A0195 for ; Wed, 17 Jun 2015 05:10:52 +0000 (UTC) Received: by oigx81 with SMTP id x81so26661861oig.1 for ; Tue, 16 Jun 2015 22:10:52 -0700 (PDT) X-Gm-Message-State: ALoCoQnhyw6zx+5ohYkbwrx7Ksmcf3v/x8Sy7g2rd8ew2PfsglhZfw8+wjIKTjfRGqelM819WDP0 MIME-Version: 1.0 X-Received: by 10.60.130.167 with SMTP id of7mr3142743oeb.85.1434517852069; Tue, 16 Jun 2015 22:10:52 -0700 (PDT) Received: by 10.202.220.130 with HTTP; Tue, 16 Jun 2015 22:10:52 -0700 (PDT) In-Reply-To: References: Date: Tue, 16 Jun 2015 22:10:52 -0700 Message-ID: Subject: Re: cmdline and docker entrypoints From: Bill Farner To: "dev@aurora.apache.org" Content-Type: multipart/alternative; boundary=089e013a1116ff466c0518afb687 --089e013a1116ff466c0518afb687 Content-Type: text/plain; charset=UTF-8 Did you ever figure this out? The entrypoint will indeed be replaced, and the command supplied in the Aurora configuration will be used. I can see how this might be unexpected, especially when using an off-the-shelf docker container. -=Bill On Sat, May 16, 2015 at 8:32 PM, Mauricio Garavaglia < mauriciogaravaglia@gmail.com> wrote: > Hi guys, > > When I create a job using a docker container the entrypoint is overriden to > launch the thermos executor. To workaround this, I'm inspecting the image > I'm about to use, to get the entrypoint and cmd which then I use in as the > process cmdline. > > I'm curious, how do you guys manage it? > --089e013a1116ff466c0518afb687--