You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ehsan Kiani Far (Jira)" <ji...@apache.org> on 2023/07/07 13:52:00 UTC

[jira] [Created] (IGNITE-19934) Improve s390x (and other arches) dockerfile

Ehsan Kiani Far created IGNITE-19934:
----------------------------------------

             Summary: Improve s390x (and other arches) dockerfile
                 Key: IGNITE-19934
                 URL: https://issues.apache.org/jira/browse/IGNITE-19934
             Project: Ignite
          Issue Type: Improvement
          Components: build
         Environment: s390x - Multi-Arch
            Reporter: Ehsan Kiani Far


While I was working with the s390x version of the Apache Ignite docker image, I observed a few issues that worth considering. 
 # The s390x image uses JDK instead of JRE which makes the image unnecessarily large 

 # The “EXPOSE” clause of the s390x dockerfile misses 10800 and 8080 ports 

 # The docker readme ([https://github.com/apache/ignite/tree/master/deliveries/docker/apache-ignite#readme]) Instructs to download and unpack the Ignite binary in the docker module but the s390x dockerfile accepts a version argument and downloads it from the file server. 

The X86-64 dockerfile ([https://github.com/apache/ignite/blob/master/deliveries/docker/apache-ignite/x86_64/Dockerfile]) uses “eclipse-temuring” base image which supports 7 different architectures (some versions of it) and can be used for multi-arch build with very little changes. The only required change would be changing the base image version to “11-jre” and remove the “add bash” command since that image already has bash. This change would eliminate the need for having a docker image for each architecture. 

I used the x86-64 dockerfile with the suggested changes to build on s390x and it worked fine. I can submit my patch file if it helps. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)