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 < mauriciogaravag...@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? >
