[ 
https://issues.apache.org/jira/browse/GEODE-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280872#comment-17280872
 ] 

Owen Nichols commented on GEODE-8412:
-------------------------------------

As an Apache open-source project, the official release artifact of Geode is the 
Geode source tarball.  However various members of the Geode community often 
create derivative works, including conveniences like pre-compiled binaries, 
dockerhub packagings, etc.

Geode is written in Java to maximize portability.  If you're interested in 
trying it on s390x, go for it!

I would recommend using the latest Dockerfile, which is linked from 
[https://hub.docker.com/r/apachegeode/geode/] (because Geode releases from 
support branches, not from develop, the copy of this file you found on develop 
is more like a template--not intended to be used directly)

You should be able to edit the Dockerfile, change the first line to a suitable 
base image containing JDK8 or later (e.g. {{FROM s390x/openjdk:11-jdk}}), and 
publish it to your own docker account if desired.

I have not heard any plans discussed on the geode dev list to publish 
additional convenience images to dockerhub, but you could certainly start that 
discussion thread, and if the community reaction is favorable, you could submit 
a PR to add that to the release scripts.

> s390x support for docker image
> ------------------------------
>
>                 Key: GEODE-8412
>                 URL: https://issues.apache.org/jira/browse/GEODE-8412
>             Project: Geode
>          Issue Type: New Feature
>          Components: general
>            Reporter: snehal
>            Priority: Major
>
> Hi,
> I am able to successfully build ApacheGeode image on s390x architecture using 
> [https://github.com/apache/geode/blob/develop/docker/Dockerfile]  Dockerfile 
> without any modifications.
> Is there any plan to support s390x docker image?
> It would be nice to just pull s390x arch image from Dockerhub.
>  
> Thanks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to