aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-657) Executor should expose thermos sandbox directory location configuration
Date Wed, 09 Dec 2015 21:31:11 GMT

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

Bill Farner commented on AURORA-657:
------------------------------------

I'm not sure how complicated the change is, but i can act as default reviewer if you put together
a patch.

> Executor should expose thermos sandbox directory location configuration
> -----------------------------------------------------------------------
>
>                 Key: AURORA-657
>                 URL: https://issues.apache.org/jira/browse/AURORA-657
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Jay Buffington
>            Assignee: Zhitao Li
>
> Currently the aurora executor hardcodes the --sandbox value that it passes to thermos_runner
when it execs it.  It always uses {{$(pwd)/sandbox}}
> This is a problem with the docker containerizer changes I'm working on for AURORA-633.
 The executor is getting started inside the docker container.  The working directory for the
container is set when the image is built by setting {{WORKDIR}} in the Dockerfile.  It defaults
to /
> This means that the sandbox directory that the thermos runner creates is being created
in {{/sandbox}}.  I want it to be created in {{$MESOS_SANDBOX/sandbox}}, and I don't want
to override the {{WORKDIR}} the user set.
> My suggestion is to add some configuration to aurora executor to control the value for
--sandbox that is passed to thermos_runner.  How about an environment variable called {{AURORA_SANDBOX}}?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message