aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kasisnu Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1540) Thermos should pass environment variables set for container to process being monitored
Date Wed, 09 Dec 2015 17:25:10 GMT

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

Kasisnu Singh commented on AURORA-1540:
---------------------------------------

[~wfarner] I have a patch for this I haven't had a chance to push out yet. Adds a {{--preserve_env}}
option to the runner. It's late in my tz. Can have it up for review by tomorrow. Also, is
there a need to strip out mesos related env variables?

> Thermos should pass environment variables set for container to process being monitored
> --------------------------------------------------------------------------------------
>
>                 Key: AURORA-1540
>                 URL: https://issues.apache.org/jira/browse/AURORA-1540
>             Project: Aurora
>          Issue Type: Story
>          Components: Docker, Thermos
>            Reporter: Kasisnu Singh
>            Assignee: Kasisnu Singh
>
> Thermos currently strips almost all environment variables for the process being monitored
by it. This breaks the existing pattern for docker containers where environment variables
can be specified with a {{--env}} flag or as part of a {{docker build}} and then have them
be available to the processes running inside the container.
> All environment variables that are not mesos related should be made available to processes
inside a container.



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

Mime
View raw message