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 <ches...@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
