You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flink.apache.org by Oran Shuster <or...@houzz.com> on 2021/08/09 22:43:21 UTC
Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Our 1.13.1 k8s deployments started failing with
tandard_init_linux.go:228: exec user process caused: exec format error
Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
linux/arm64
Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
Re: Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Posted by Oran Shuster <or...@houzz.com>.
Ah yes, the M1...
There is a way to generate amd64 images on M1 machines
https://blog.jaimyn.dev/how-to-build-multi-architecture-docker-images-on-an-m1-mac/#tldr;
but yeah, the architecture change makes a lot of mistakes in our company as well
As for why i am using the apache/flink repo - there was a fix for a 1.12 bug with k8s HA that wanted to move to fast and the updated images were not available on the regular flink repo. We just stayed there since
On 2021/08/11 08:53:25, Jingsong Li <ji...@gmail.com> wrote:
> Hi Oran and Chesnay,
>
> I think it should be my problem. The docker image I generated on the
> computer with the macbook M1 will lead to the image of arm64 (When
> releasing 1.12.5).
>
> We will regenerate the image of 1.13.1 on the Intel x86 machine.
>
> I'm very sorry.
>
> Best,
> Jingsong
>
> On Tue, Aug 10, 2021 at 10:25 PM Chesnay Schepler <ch...@apache.org> wrote:
> >
> > Ah, yes I was looking at the wrong one. I'll figure out what happened
> > and get the situation fixed.
> >
> > Overall though, I'd recommend to rely on https://hub.docker.com/_/flink.
> >
> > On 10/08/2021 16:04, Oran Shuster wrote:
> > > Are you sure you are looking at the correct repo?
> > > flink has 2 docker repos for it's images - flink and apache/flink
> > > for flink, everything is fine https://hub.docker.com/_/flink?tab=tags&page=1&ordering=last_updated&name=1.13.1
> > > But for apache/flink (which is still official, and updated faster then the "regular" flink one), the 1.13.1 images are still arm64 https://hub.docker.com/r/apache/flink/tags?page=1&ordering=last_updated&name=1.13.1
> > >
> > > On 2021/08/10 07:13:21, Chesnay Schepler <ch...@apache.org> wrote:
> > >> Looking at the dockerhub page know, all 1.13.1 images are listed as
> > >> amd64, with the last push being 5 days ago.
> > >> Perhaps some error happened during the rebuild, which has since been
> > >> corrected?
> > >>
> > >> On 10/08/2021 00:43, Oran Shuster wrote:
> > >>> Our 1.13.1 k8s deployments started failing with
> > >>> tandard_init_linux.go:228: exec user process caused: exec format error
> > >>> Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
> > >>> Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
> > >>> linux/arm64
> > >>>
> > >>> Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
> > >>>
> > >>
> >
>
>
> --
> Best, Jingsong Lee
>
Re: Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Posted by Jingsong Li <ji...@gmail.com>.
Hi Oran and Chesnay,
I think it should be my problem. The docker image I generated on the
computer with the macbook M1 will lead to the image of arm64 (When
releasing 1.12.5).
We will regenerate the image of 1.13.1 on the Intel x86 machine.
I'm very sorry.
Best,
Jingsong
On Tue, Aug 10, 2021 at 10:25 PM Chesnay Schepler <ch...@apache.org> wrote:
>
> Ah, yes I was looking at the wrong one. I'll figure out what happened
> and get the situation fixed.
>
> Overall though, I'd recommend to rely on https://hub.docker.com/_/flink.
>
> On 10/08/2021 16:04, Oran Shuster wrote:
> > Are you sure you are looking at the correct repo?
> > flink has 2 docker repos for it's images - flink and apache/flink
> > for flink, everything is fine https://hub.docker.com/_/flink?tab=tags&page=1&ordering=last_updated&name=1.13.1
> > But for apache/flink (which is still official, and updated faster then the "regular" flink one), the 1.13.1 images are still arm64 https://hub.docker.com/r/apache/flink/tags?page=1&ordering=last_updated&name=1.13.1
> >
> > On 2021/08/10 07:13:21, Chesnay Schepler <ch...@apache.org> wrote:
> >> Looking at the dockerhub page know, all 1.13.1 images are listed as
> >> amd64, with the last push being 5 days ago.
> >> Perhaps some error happened during the rebuild, which has since been
> >> corrected?
> >>
> >> On 10/08/2021 00:43, Oran Shuster wrote:
> >>> Our 1.13.1 k8s deployments started failing with
> >>> tandard_init_linux.go:228: exec user process caused: exec format error
> >>> Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
> >>> Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
> >>> linux/arm64
> >>>
> >>> Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
> >>>
> >>
>
--
Best, Jingsong Lee
Re: Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Posted by Chesnay Schepler <ch...@apache.org>.
Ah, yes I was looking at the wrong one. I'll figure out what happened
and get the situation fixed.
Overall though, I'd recommend to rely on https://hub.docker.com/_/flink.
On 10/08/2021 16:04, Oran Shuster wrote:
> Are you sure you are looking at the correct repo?
> flink has 2 docker repos for it's images - flink and apache/flink
> for flink, everything is fine https://hub.docker.com/_/flink?tab=tags&page=1&ordering=last_updated&name=1.13.1
> But for apache/flink (which is still official, and updated faster then the "regular" flink one), the 1.13.1 images are still arm64 https://hub.docker.com/r/apache/flink/tags?page=1&ordering=last_updated&name=1.13.1
>
> On 2021/08/10 07:13:21, Chesnay Schepler <ch...@apache.org> wrote:
>> Looking at the dockerhub page know, all 1.13.1 images are listed as
>> amd64, with the last push being 5 days ago.
>> Perhaps some error happened during the rebuild, which has since been
>> corrected?
>>
>> On 10/08/2021 00:43, Oran Shuster wrote:
>>> Our 1.13.1 k8s deployments started failing with
>>> tandard_init_linux.go:228: exec user process caused: exec format error
>>> Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
>>> Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
>>> linux/arm64
>>>
>>> Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
>>>
>>
Re: Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Posted by Oran Shuster <or...@houzz.com>.
Are you sure you are looking at the correct repo?
flink has 2 docker repos for it's images - flink and apache/flink
for flink, everything is fine https://hub.docker.com/_/flink?tab=tags&page=1&ordering=last_updated&name=1.13.1
But for apache/flink (which is still official, and updated faster then the "regular" flink one), the 1.13.1 images are still arm64 https://hub.docker.com/r/apache/flink/tags?page=1&ordering=last_updated&name=1.13.1
On 2021/08/10 07:13:21, Chesnay Schepler <ch...@apache.org> wrote:
> Looking at the dockerhub page know, all 1.13.1 images are listed as
> amd64, with the last push being 5 days ago.
> Perhaps some error happened during the rebuild, which has since been
> corrected?
>
> On 10/08/2021 00:43, Oran Shuster wrote:
> > Our 1.13.1 k8s deployments started failing with
> > tandard_init_linux.go:228: exec user process caused: exec format error
> > Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
> > Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
> > linux/arm64
> >
> > Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
> >
>
>
Re: Apache/flink 1.13.1 images re-pushed and in arm64 arch?
Posted by Chesnay Schepler <ch...@apache.org>.
Looking at the dockerhub page know, all 1.13.1 images are listed as
amd64, with the last push being 5 days ago.
Perhaps some error happened during the rebuild, which has since been
corrected?
On 10/08/2021 00:43, Oran Shuster wrote:
> Our 1.13.1 k8s deployments started failing with
> tandard_init_linux.go:228: exec user process caused: exec format error
> Not understanding how an old image with an old depoyment starts failing like that i looked at the apache/flink dockerhub page.
> Although 1.13.1 was released more than a month ago, all the images (apart from 1.13.1-scala_2.11-java11) were pushed 6 days ago and their architecture changed from linux/amd64 to
> linux/arm64
>
> Luckily the "official" flink images (that were also pushed 5-6 days ago) are still amd64 and can be used
>