[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[Stephen Degler (JIRA)]

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

Stephen Degler commented on MESOS-3787:
---------------------------------------

Ah I see:
Something like this:        "volumes": [
            {
                "containerPath": "${KRB5CCNAME}",
                "hostPath": "${KRB5CCNAME}",
                "mode": "RO"
            }
      ]

was transformed differently because it was treated as if it had a relative path?

-v 
/home/tsram/mesos-slave/work/slaves/20151103-163728-312349868-5050-3623-S0/frameworks/20151103-163728-312349868-5050-3623-0000/executors/test-13.6d001069-8260-11e5-830c-fa163ecc88fa/runs/d7bb20ed-970d-4aab-bc84-ddf76361741e//tmp/Jj3TH1:/tmp/Jj3TH1:ro

This is due to something about handling relative vs absolute paths.

-v /tmp/Jj3TH1:/tmp/Jj3TH1:ro

Would probably work just fine.

So your patch is good but then the logic with handling relative paths is 
mangled by the presence of the variables.


> As a developer, I'd like to be able to expand environment variables through 
> the Docker executor.
> ------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-3787
>                 URL: https://issues.apache.org/jira/browse/MESOS-3787
>             Project: Mesos
>          Issue Type: Wish
>            Reporter: John Garcia
>              Labels: mesosphere
>         Attachments: mesos.patch, test-example.json
>
>
> We'd like to have expanded variables usable in [the json files used to create 
> a Marathon app, hence] the Task's CommandInfo, so that the executor is able 
> to detect the correct values at runtime.



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