"Repositories failed error" when building Elasticsearch image

[karlhendrik]

I'm trying to build elasticsearch:7.3.2 image(from master) on Rasbian Buster with aarch64 kernel in RPi4 but it fails and throws error below.

My environment
uname -a output:
Linux RPi4 4.19.79-v8+ #1273 SMP PREEMPT Fri Oct 11 18:35:44 BST 2019 aarch64 GNU/Linux

docker --version output:
Docker version 19.03.4, build 9013bf5

Error while building

Step 14/26 : RUN for iter in {1..10}; do yum update -y &&     yum install -y nc &&     yum clean all && exit_code=0 && break || exit_code=$? && echo "yum error: retry $iter in 10s" && sleep 10; done;     (exit $exit_code)
 ---> Running in f871fe58256c
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=<repoid> ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>
        or
            subscription-manager repos --disable=<repoid>

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: centos-kernel/7/aarch64
yum error: retry 1 in 10s

Is there something wrong with my environment?

Tried with that argument : https://stackoverflow.com/questions/49779741/yum-update-fails-centos-7-dockerbuild

No effect still.

But no effect while building.

[gagara]

is it always reproducible? If you restart the build will it fail at the same point? (could be some temp network issue).
I don't think you have docker-network problem as it is not the first setup during the build which uses network to download something.

[karlhendrik]

is it always reproducible? If you restart the build will it fail at the same point? (could be some temp network issue).
I don't think you have docker-network problem as it is not the first setup during the build which uses network to download something.

Yep, tried switching CentOS base image to different architecture (arm64v8 & arm32v7). Finally i figured that switching to alpine based Dockerfile worked and built final image with builx and pushed it to Docker hub.

Here is final image Elasticsearch 6.8.2: https://hub.docker.com/r/karlhendrik/elasticsearch