You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Joshua Griffith (JIRA)" <ji...@apache.org> on 2017/05/12 15:26:04 UTC

[jira] [Updated] (FLINK-6572) Make configuration properties available as env vars in Docker image

     [ https://issues.apache.org/jira/browse/FLINK-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Griffith updated FLINK-6572:
-----------------------------------
    Summary: Make configuration properties available as env vars in Docker image  (was: Make Flink configuration properties available as env vars in Docker image)

> Make configuration properties available as env vars in Docker image
> -------------------------------------------------------------------
>
>                 Key: FLINK-6572
>                 URL: https://issues.apache.org/jira/browse/FLINK-6572
>             Project: Flink
>          Issue Type: Improvement
>          Components: Docker
>    Affects Versions: 1.2.1
>            Reporter: Joshua Griffith
>            Priority: Minor
>
> We run Flink in containers in production and it has been convenient to have all of Flink's configuration options available as environment variables so a separate configuration volume is not required. In our image we [grab the options from the config documentation|https://github.com/orgsync/docker-flink/blob/2abc0bf2b93238e4d1895d4ada0e8f6a72b577cf/Dockerfile#L33-L40] and [load them into the configuration file in the entrypoint|https://github.com/orgsync/docker-flink/blob/2abc0bf2b93238e4d1895d4ada0e8f6a72b577cf/entrypoint.sh#L32-L50]. While this method is not ideal, I think this feature would be useful in the official Docker image.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)