You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zhitao Li (JIRA)" <ji...@apache.org> on 2015/12/09 19:47:11 UTC
[jira] [Assigned] (AURORA-657) Executor should expose thermos
sandbox directory location configuration
[ https://issues.apache.org/jira/browse/AURORA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhitao Li reassigned AURORA-657:
--------------------------------
Assignee: Zhitao Li
> 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)