flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismaël Mejía (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FLINK-3026) Publish the flink docker container to the docker registry
Date Sun, 12 Mar 2017 13:00:05 GMT

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

Ismaël Mejía commented on FLINK-3026:

I saw the images you built, probably it is a better idea to enable automated builds for the
repo so those are rebuilt once we push the changes in github, have you tried this?

And, I have another proposition to make, maybe it is a better idea to create a github organization
for this, and move the repo there, to end up with something like (docker-flink/docker-flink)
instead of your personal account or the dataartisans one, that way we can share the maintainance,
and I or other future maintainer can trigger the builds too from docker hub if he has the
permissions. Currently I can’t trigger the builds of docker-flink because they only let
your own account and the organizations you belong too.

> Publish the flink docker container to the docker registry
> ---------------------------------------------------------
>                 Key: FLINK-3026
>                 URL: https://issues.apache.org/jira/browse/FLINK-3026
>             Project: Flink
>          Issue Type: Task
>          Components: Build System, Docker
>            Reporter: Omer Katz
>            Assignee: Patrick Lucas
>              Labels: Deployment, Docker
> There's a dockerfile that can be used to build a docker container already in the repository.
It'd be awesome to just be able to pull it instead of building it ourselves.
> The dockerfile can be found at https://github.com/apache/flink/tree/master/flink-contrib/docker-flink
> It also doesn't point to the latest version of Flink which I fixed in https://github.com/apache/flink/pull/1366

This message was sent by Atlassian JIRA

View raw message