flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie Grier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5635) Improve Docker tooling to make it easier to build images and launch Flink via Docker tools
Date Thu, 26 Jan 2017 02:06:26 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839036#comment-15839036

Jamie Grier commented on FLINK-5635:

[~greghogan] I actually wasn't aware of [FLINK-4326].  However there does seem to be some
overlap.  There is also [FLINK-5634] and an associated PR which specifically addresses enabling
logging to stdout rather than to a file.  However, neither of these two issues addresses running
Flink processes in the foreground and avoiding forking as in [FLINK-4326].  I think this remains
a separate issue that may need to be addressed.

My main motivation in both of these JIRA issues and associated PRs was in providing a better
Flink on Docker experience and providing some example scripts of how to run Flink properly
in container-based environments.  I would also like to get some "official" Flink Docker images
published once we're satisfied with them.

> Improve Docker tooling to make it easier to build images and launch Flink via Docker
> ------------------------------------------------------------------------------------------
>                 Key: FLINK-5635
>                 URL: https://issues.apache.org/jira/browse/FLINK-5635
>             Project: Flink
>          Issue Type: Improvement
>          Components: Docker
>    Affects Versions: 1.2.0
>            Reporter: Jamie Grier
>            Assignee: Jamie Grier
>             Fix For: 1.2.0
> This is a bit of a catch-all ticket for general improvements to the Flink on Docker experience.
> Things to improve:
>   - Make it possible to build a Docker image from your own flink-dist directory as well
as official releases.
>   - Make it possible to override the image name so a user can more easily publish these
images to their Docker repository
>   - Provide scripts that show how to properly run on Docker Swarm or similar environments
with overlay networking (Kubernetes) without using host networking.
>   - Log to stdout rather than to files.
>   - Work properly with docker-compose for local deployment as well as production deployments

This message was sent by Atlassian JIRA

View raw message