Matthias Pohl created FLINK-31210:
-
Summary: Azure Pipelines report warning on "no space left on
device" in Restore Docker images step
Key: FLINK-31210
URL: https://issues.apache.org/jira/browse/F
Chesnay Schepler created FLINK-29137:
Summary: Switch docker images to eclipse temurin base
Key: FLINK-29137
URL: https://issues.apache.org/jira/browse/FLINK-29137
Project: Flink
Issue
flink-kubernetes-operator has already been using github
>> >> packages to deliver the snapshot images[1].
>> >>
>> >> [1].
>> >>
>> >>
>> https://github.com/apache/flink-kubernetes-operator/pkgs/container/flink-kubernetes-operator
&g
Alexander Fedulov created FLINK-27671:
-
Summary: Publish SNAPSHOT docker images
Key: FLINK-27671
URL: https://issues.apache.org/jira/browse/FLINK-27671
Project: Flink
Issue Type
> >> > +1 to public Flink Docker image for snapshot.
> >> >
> >> > Best,
> >> > Jingsong
> >> >
> >> > On Fri, Apr 22, 2022 at 2:23 AM Alexander Fedulov
> >> > wrote:
> >> > >
> >> > >
t;>
>> Best,
>> Yang
>>
>> Jingsong Li 于2022年4月22日周五 10:43写道：
>>
>> > +1 to public Flink Docker image for snapshot.
>> >
>> > Best,
>> > Jingsong
>> >
>> > On Fri, Apr 22, 2022 at 2:23 AM Alexander Fedulov
>>
4月22日周五 10:43写道：
>
> > +1 to public Flink Docker image for snapshot.
> >
> > Best,
> > Jingsong
> >
> > On Fri, Apr 22, 2022 at 2:23 AM Alexander Fedulov
> > wrote:
> > >
> > > Hi everyone,
> > >
> > > in the scope of work
for snapshot.
>
> Best,
> Jingsong
>
> On Fri, Apr 22, 2022 at 2:23 AM Alexander Fedulov
> wrote:
> >
> > Hi everyone,
> >
> > in the scope of work on externalizing connectors [1] it became evident
> that
> > we need to add the process of releasi
+1 to public Flink Docker image for snapshot.
Best,
Jingsong
On Fri, Apr 22, 2022 at 2:23 AM Alexander Fedulov
wrote:
>
> Hi everyone,
>
> in the scope of work on externalizing connectors [1] it became evident that
> we need to add the process of releasing SNAPSHOT (nightly) Dock
Hi everyone,
in the scope of work on externalizing connectors [1] it became evident that
we need to add the process of releasing SNAPSHOT (nightly) Docker images
for Flink. Let me briefly explain why this is the case:
- currently, our container-based E2E tests rely on building Flink Docker
images
ek wrote:
Hi,
I did some quick prototyping on the slimmed down docker images, and I was
able to cut the docker image size by ~40% with a minimum effort [1] (using
a multi-stage build + trimming examples / opt + using slimmed down JRE
image).
I think this might be a low hanging fruit for reduci
c 22, 2021 at 2:43 PM David Morávek wrote:
> Hi,
>
> I did some quick prototyping on the slimmed down docker images, and I was
> able to cut the docker image size by ~40% with a minimum effort [1] (using
> a multi-stage build + trimming examples / opt + using slimmed down JRE
&
Hi,
I did some quick prototyping on the slimmed down docker images, and I was
able to cut the docker image size by ~40% with a minimum effort [1] (using
a multi-stage build + trimming examples / opt + using slimmed down JRE
image).
I think this might be a low hanging fruit for reducing MTTR in
Matthias created FLINK-24075:
Summary: Apache Flink 1.13.1 Docker images are published for
linux/arm
Key: FLINK-24075
URL: https://issues.apache.org/jira/browse/FLINK-24075
Project: Flink
Issue
Dawid Wysakowicz created FLINK-22386:
Summary: Introduce cache for docker images
Key: FLINK-22386
URL: https://issues.apache.org/jira/browse/FLINK-22386
Project: Flink
Issue Type: Task
Hi,
We have created an "apache/flink-statefun" Dockerhub repository managed by
the Flink PMC, at:
https://hub.docker.com/r/apache/flink-statefun
The images for the latest stable StateFun release, 2.2.2, have already been
pushed there.
Going forward, it will be part of the release process to make
Robert Metzger created FLINK-20929:
--
Summary: Add automated deployment of nightly docker images
Key: FLINK-20929
URL: https://issues.apache.org/jira/browse/FLINK-20929
Project: Flink
Issue
Nazar Volynets created FLINK-20775:
--
Summary: Missed Docker Images Flink 1.12
Key: FLINK-20775
URL: https://issues.apache.org/jira/browse/FLINK-20775
Project: Flink
Issue Type: Bug
David Pichler created FLINK-20754:
-
Summary: Flink 1.12 docker images not present on Dockerhub
Key: FLINK-20754
URL: https://issues.apache.org/jira/browse/FLINK-20754
Project: Flink
Issue
Piotr Gwiazda created FLINK-20632:
-
Summary: Missing docker images for 1.12 releas
Key: FLINK-20632
URL: https://issues.apache.org/jira/browse/FLINK-20632
Project: Flink
Issue Type: Bug
Julius Michaelis created FLINK-19502:
Summary: Flink docker images: allow specifying arbitrary
configuration values through environment
Key: FLINK-19502
URL: https://issues.apache.org/jira/browse/FLINK-19502
>
> On Fri, Feb 21, 2020 at 11:26 AM Chesnay Schepler <
> ches...@apache.org>
> wrote:
>
> I've added a "Release System / Docker" component.
>
> On 21/02/2020 11:19, Patrick Lucas wrote:
> Hi,
>
> Could someone with permissions add a new com
On 21/02/2020 11:19, Patrick Lucas wrote:
Hi,
Could someone with permissions add a new component to the FLINK
project
in
Jira for the Docker images <
https://github.com/apache/flink-docker
?
There is already a "Deployment / Docker" component, but that's
not
quite
the same as mainten
wrote:
> > >
> > > > Thanks, Chesnay!
> > > >
> > > > On Fri, Feb 21, 2020 at 11:26 AM Chesnay Schepler <
> ches...@apache.org>
> > > > wrote:
> > > >
> > > > > I've added a "Release System / Docker&q
;
> > > On Fri, Feb 21, 2020 at 11:26 AM Chesnay Schepler
> > > wrote:
> > >
> > > > I've added a "Release System / Docker" component.
> > > >
> > > > On 21/02/2020 11:19, Patrick Lucas wrote:
> &
eb 21, 2020 at 11:26 AM Chesnay Schepler
> > wrote:
> >
> > > I've added a "Release System / Docker" component.
> > >
> > > On 21/02/2020 11:19, Patrick Lucas wrote:
> > > > Hi,
> > > >
> > > > Could someone with p
ler
> wrote:
>
> > I've added a "Release System / Docker" component.
> >
> > On 21/02/2020 11:19, Patrick Lucas wrote:
> > > Hi,
> > >
> > > Could someone with permissions add a new component to the FLINK project
> >
could provide
the daily updating snapshot for docker image, it will be very helpful for
the users
who want to have a taste of new features or benefit from urgent hotfix.
Best,
Yang
Ismaël Mejía 于2020年4月28日周二 下午11:07写道：
To me this means that the docker images should be released at the same
features or benefit from urgent hotfix.
Best,
Yang
Ismaël Mejía 于2020年4月28日周二 下午11:07写道：
> > To me this means that the docker images should be released at the same
> time the other artifacts are released. This also includes shapshot
> releases. So the build of the docker images
> To me this means that the docker images should be released at the same time
> the other artifacts are released. This also includes shapshot releases. So
> the build of the docker images should be an integral part of the build.
This is already the case since the last release, what th
iels,
I think Robert was referring to the fact that Apache considers only
the source release to be "the release", everything else is called
convenience release.
Best,
Aljoscha
On 27.04.20 19:43, Niels Basjes wrote:
Hi,
In my opinion the docker images are essentially simply dif
Hi Niels,
I think Robert was referring to the fact that Apache considers only the
source release to be "the release", everything else is called
convenience release.
Best,
Aljoscha
On 27.04.20 19:43, Niels Basjes wrote:
Hi,
In my opinion the docker images are essentially simply d
Hi,
In my opinion the docker images are essentially simply differently packed
binary releases.
This becomes more true when in the future deploying a Flink application to
kubernetes simply pulls the correct binary from a docker hub. Because of
these kinds of use cases I disagree with Robert that
Thanks for starting the thread!
I would consider the docker images of Flink convenience binary releases
that can happen any time. I believe a simplified, but formal release
process would be appropriate (preview / staging images for the community to
validate & vote, then release to docker
PR) that is the release of docker images
independent of major Flink releases.
In the past when the docker images were maintained outside of the Apache
repository we usually did intermediary releases to fix issues or to add new
functionalities that were independent of the Flink releases and
the docker unification thread (and in some other PR) that is the release
of docker images independent of major Flink releases. In the past when the
docker images were maintained outside of the Apache repository we usually did
intermediary releases to fix issues or to add new functionalities that
shortly mentioned
during the docker unification thread (and in some other PR) that is the release
of docker images independent of major Flink releases. In the past when the
docker images were maintained outside of the Apache repository we usually did
intermediary releases to fix issues or to add
Hello,
I wanted to discuss about a subject that was shortly mentioned during the docker
unification thread (and in some other PR) that is the release of docker images
independent of major Flink releases.
In the past when the docker images were maintained outside of the Apache
repository we
Ismaël Mejía created FLINK-16846:
Summary: Add docker images with python
Key: FLINK-16846
URL: https://issues.apache.org/jira/browse/FLINK-16846
Project: Flink
Issue Type: Improvement
Ismaël Mejía created FLINK-16260:
Summary: Add Java 11 based version of the docker images
Key: FLINK-16260
URL: https://issues.apache.org/jira/browse/FLINK-16260
Project: Flink
Issue Type
Thanks, Chesnay!
On Fri, Feb 21, 2020 at 11:26 AM Chesnay Schepler
wrote:
> I've added a "Release System / Docker" component.
>
> On 21/02/2020 11:19, Patrick Lucas wrote:
> > Hi,
> >
> > Could someone with permissions add a new component to the FLINK p
I've added a "Release System / Docker" component.
On 21/02/2020 11:19, Patrick Lucas wrote:
Hi,
Could someone with permissions add a new component to the FLINK project in
Jira for the Docker images <https://github.com/apache/flink-docker>?
There is already a "Depl
Hi,
Could someone with permissions add a new component to the FLINK project in
Jira for the Docker images <https://github.com/apache/flink-docker>?
There is already a "Deployment / Docker" component, but that's not quite
the same as maintenance/improvements on the flink-d
Stephan Ewen created FLINK-15671:
Summary: Provide one place for Docker Images with all supported
cluster modes
Key: FLINK-15671
URL: https://issues.apache.org/jira/browse/FLINK-15671
Project: Flink
Konstantin Knauf created FLINK-12546:
Summary: Base Docker images on `library/flink`
Key: FLINK-12546
URL: https://issues.apache.org/jira/browse/FLINK-12546
Project: Flink
Issue Type
Leonid Ishimnikov created FLINK-9695:
Summary: Add option for Mesos executor to forcefully pull Docker
images
Key: FLINK-9695
URL: https://issues.apache.org/jira/browse/FLINK-9695
Project: Flink
ink itself. This is a very common
practice and applies to most other popular "official" images hosted on
Docker Hub.
--
Patrick Lucas
On Wed, Dec 20, 2017 at 4:20 AM, Felix Cheung
wrote:
> Hi!
>
> Is there a reason the official docker images
> https://hub.docker.com/r/_/flink
Hi!
Is there a reason the official docker images
https://hub.docker.com/r/_/flink/
Has sources in a different repo
https://github.com/docker-flink/docker-flink
?
Greg Hogan created FLINK-6616:
-
Summary: Clarify provenance of official Docker images
Key: FLINK-6616
URL: https://issues.apache.org/jira/browse/FLINK-6616
Project: Flink
Issue Type: Improvement
be to integrate the docker images into the Flink release
> process?
>
> Ideally, we could provide something like a staging directory for the docker
> images, so that we can include them into the vote.
> Once the vote has passed, the images will be made public through docker hub
&g
How hard would it be to integrate the docker images into the Flink release
process?
Ideally, we could provide something like a staging directory for the docker
images, so that we can include them into the vote.
Once the vote has passed, the images will be made public through docker hub
and apache
aël Mejía
> wrote:
> >>
> >> > Hello,
> >> >
> >> > I am absolutely happy to see that this is finally happening!
> >> > We have a really neat image right now and it is great that it will be
> >> > soon so easy to use.
> >&g
gt;> > >
>> > > You can see the aforementioned squirrel here
>> > > <https://activerain-store.s3.amazonaws.com/image_store/
>> > uploads/8/7/6/3/9/ar12988558393678.JPG>
>> > > .
>> > >
>> > > --
>> > > Patr
17 at 11:00 AM, Ismaël Mejía wrote:
>
> > Hello,
> >
> > I am absolutely happy to see that this is finally happening!
> > We have a really neat image right now and it is great that it will be
> > soon so easy to use.
> >
> > One extra thing to mention i
ight now and it is great that it will be
> soon so easy to use.
>
> One extra thing to mention is that Flink will have now two docker
> images, one based on debian and the other one based on Alpine as most
> official java-based projects do.
>
> In the future we expect to improv
Hello,
I am absolutely happy to see that this is finally happening!
We have a really neat image right now and it is great that it will be
soon so easy to use.
One extra thing to mention is that Flink will have now two docker
images, one based on debian and the other one based on Alpine as most
> As part of an ongoing effort to improve the experience of using Flink on
> Docker, some work has been done over the last two months to publish
> official Flink Docker images to Docker Hub. The goal in the short term is
> to make running a simple Flink cluster (almost) as easy as runnin
As part of an ongoing effort to improve the experience of using Flink on
Docker, some work has been done over the last two months to publish
official Flink Docker images to Docker Hub. The goal in the short term is
to make running a simple Flink cluster (almost) as easy as running docker
run flink
kathleen sharp created FLINK-6300:
-
Summary: PID1 of docker images does not behave correctly
Key: FLINK-6300
URL: https://issues.apache.org/jira/browse/FLINK-6300
Project: Flink
Issue Type
59 matches
Mail list logo
