[
https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988733#comment-14988733
]
Stephen Degler commented on MESOS-3787:
---------------------------------------
Also the shell footprint isn't a big deal, however inserting exec after bash -c
should suffice to get rid of it.
I think problem is that the variables are quoted in some way that bash is not
expanding them.
The ${KRB5CCNAME} should already be expanded when you see it in ps.
Otherwise, I have no problem with this approach.
-------- Original message --------
From: "haosdent (JIRA)" <[email protected]>
Date: 11/03/2015 8:39 PM (GMT-05:00)
To: [email protected]
Subject: [jira] [Commented] (MESOS-3787) As a developer, I'd like to be able
to expand environment variables through the Docker executor.
[
https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988693#comment-14988693
]
haosdent commented on MESOS-3787:
---------------------------------
Because have two process?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
> 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)
