| To: | Nathan Scott <nscott@xxxxxxxxxx> |
|---|---|
| Subject: | PATCH RFC use environment to signify container name for rc scripts |
| From: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
| Date: | Mon, 16 Mar 2015 17:39:17 +1100 |
| Cc: | pcp <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
Nathan, dockerfiles have an ENV feature, which can pass an environment variable to all future "docker run" invocations. It can also be overridden with "docker run --env whatever=something". So we could use this instead of $PCP_SYSCONF_DIR/pcp.pause. An errant or stale pcp.pause file could cause havoc (especially with QA), .. but then so could incorrect environment. Something like $PCP_CONTAINER_NAME might prove very useful in contexts other than rc scripts too. Thoughts?
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates: qa, container updates, Nathan Scott |
|---|---|
| Next by Date: | Re: PATCH RFC use environment to signify container name for rc scripts, Frank Ch. Eigler |
| Previous by Thread: | pcp updates: qa, container updates, Nathan Scott |
| Next by Thread: | Re: PATCH RFC use environment to signify container name for rc scripts, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |