You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Daniel Krawczyk <da...@gmail.com> on 2017/01/18 16:49:32 UTC
Why task environment variables are set for executor/containerizer?
Hi,
When I set an environment variable for my task it is as well applied both
to mesos-containerizer and mesos-executor.
This may lead to problems, for example when loading dynamic libraries with
LD_PRELOAD.
Is setting task variables to executor/containerizer a bug?
Cheers,
Daniel
Re: Why task environment variables are set for executor/containerizer?
Posted by Daniel Krawczyk <da...@gmail.com>.
Thank you guys!
śr., 18 sty 2017 o 18:01 użytkownik Tomek Janiszewski <ja...@gmail.com>
napisał:
> Created issue: https://issues.apache.org/jira/browse/MESOS-6945
>
> śr., 18 sty 2017 o 17:54 użytkownik Jie Yu <yu...@gmail.com> napisał:
>
> Can you create a ticket for that? I personally want to fix that for
> command executor.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:52 PM, Jie Yu <yu...@gmail.com> wrote:
>
> Daniel,
>
> Yes, this is a tech debt in the old command executor. The new default
> executor does not have this issue.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk <da...@gmail.com>
> wrote:
>
> Hi,
>
> When I set an environment variable for my task it is as well applied both
> to mesos-containerizer and mesos-executor.
> This may lead to problems, for example when loading dynamic libraries with
> LD_PRELOAD.
>
> Is setting task variables to executor/containerizer a bug?
>
> Cheers,
> Daniel
>
>
>
>
Re: Why task environment variables are set for executor/containerizer?
Posted by Tomek Janiszewski <ja...@gmail.com>.
Created issue: https://issues.apache.org/jira/browse/MESOS-6945
śr., 18 sty 2017 o 17:54 użytkownik Jie Yu <yu...@gmail.com> napisał:
> Can you create a ticket for that? I personally want to fix that for
> command executor.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:52 PM, Jie Yu <yu...@gmail.com> wrote:
>
> Daniel,
>
> Yes, this is a tech debt in the old command executor. The new default
> executor does not have this issue.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk <da...@gmail.com>
> wrote:
>
> Hi,
>
> When I set an environment variable for my task it is as well applied both
> to mesos-containerizer and mesos-executor.
> This may lead to problems, for example when loading dynamic libraries with
> LD_PRELOAD.
>
> Is setting task variables to executor/containerizer a bug?
>
> Cheers,
> Daniel
>
>
>
>
Re: Why task environment variables are set for executor/containerizer?
Posted by Jie Yu <yu...@gmail.com>.
Can you create a ticket for that? I personally want to fix that for command
executor.
- Jie
On Wed, Jan 18, 2017 at 5:52 PM, Jie Yu <yu...@gmail.com> wrote:
> Daniel,
>
> Yes, this is a tech debt in the old command executor. The new default
> executor does not have this issue.
>
> - Jie
>
> On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk <da...@gmail.com>
> wrote:
>
>> Hi,
>>
>> When I set an environment variable for my task it is as well applied both
>> to mesos-containerizer and mesos-executor.
>> This may lead to problems, for example when loading dynamic libraries
>> with LD_PRELOAD.
>>
>> Is setting task variables to executor/containerizer a bug?
>>
>> Cheers,
>> Daniel
>>
>>
>
Re: Why task environment variables are set for executor/containerizer?
Posted by Jie Yu <yu...@gmail.com>.
Daniel,
Yes, this is a tech debt in the old command executor. The new default
executor does not have this issue.
- Jie
On Wed, Jan 18, 2017 at 5:49 PM, Daniel Krawczyk <da...@gmail.com> wrote:
> Hi,
>
> When I set an environment variable for my task it is as well applied both
> to mesos-containerizer and mesos-executor.
> This may lead to problems, for example when loading dynamic libraries with
> LD_PRELOAD.
>
> Is setting task variables to executor/containerizer a bug?
>
> Cheers,
> Daniel
>
>