[
https://issues.apache.org/jira/browse/GEODE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733327#comment-14733327
]
jun aoki commented on GEODE-60:
-------------------------------
Hi [~upthewaterspout]
>> The docker image used for building geode shouldn't contain geode.
That's right and I'm on the same page. [~markito], typically, code (or user
data, for example, like data files for database) should not be inside of Docker
container but mounted (aka volume)
{code}
docker run -it -v /path/to/geode/code:/root/geode
{code}
I had a little discussion with Bigtop team some time ago, they still create
their own docker images. e.g. https://hub.docker.com/r/bigtop/
so that just in case, let's say, 8u40-jdk is all the sudden gone from the repo
(and we don't have control of it at all), there is no impact from our business.
I have an experience where a tag of centos was gone a couple of years ago too(,
of course when things were more unstable than today).
Should we still go creating a Dockerfile , or just use what is published?
> 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.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)
