[
https://issues.apache.org/jira/browse/GEODE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790992#comment-14790992
]
jun aoki commented on GEODE-60:
-------------------------------
>> What's different in your box that makes it so big
Sorry for the confusion. I made up the CLI result, and intended to show what
image names would be created. Please discard the size etc.
I'm fine with your tree structure, but curious what should be Geode's product
image(s) and who are target audiences.
The current one (/docker/Dockerfile) is for one single container and play with
gfsh, which is good for users just trying out with Geode.
But, if you think of *real and cool* Docker use cases where a bunch of
different Geode images play and collaborate. The server image, the locator
image, and client image (I don't know what other components play a role but
probably more), which will work together with Kubernetes, or even CloudFoundry!
This will result many more Dockerfiles, I hope they all go under the same
directory (possibly dev-tools but can be docker. I'm open to suggestions)
I think there are 2 types of audiences here.
One is end users who wants to play gfsh and the other is devs like us.
End uesrs will not care where Dockerfile are and don't bother building it
either, but want to see if an built image is published(on the hub).
Devs do care where Dockerfiles are and they are the ones who actually build
images.
But regarding Geode audiences, I'm newbie and you guys know better :)
I believe we both agree to have the common Dockerfile idea and have 2 more to
do specific work. Let me work on this part now. Let me know also about the
folder structure.
> Geode build environment within Docker to enable anybody and on any OS and any
> environment can build Geode as long as there is Docker
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-60
> URL: https://issues.apache.org/jira/browse/GEODE-60
> Project: Geode
> Issue Type: Sub-task
> Components: build
> Reporter: jun aoki
> Assignee: jun aoki
> Attachments: GEODE-60-2.patch, GEODE-60-3.patch, GEODE-60-4.patch,
> GEODE-60.patch
>
>
> geode build is on gradle and seems very tidy but it still requires third
> party libraries, like Java.
> Let's have a Docker environment so that at least we have an reliable
> immutable environment and we can use it on CI on builds.apache.org
> https://builds.apache.org/view/E-G/view/Geode/
> (From my experience, It is a bit of pain to find a right environment on
> builds.a.o but Docker is a cure so far.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
