[
https://issues.apache.org/jira/browse/GEODE-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijat Upadhyay updated GEODE-1935:
------------------------------------
Attachment: docker-gemfire8.zip
Build the docker image using the command
{code}
docker build --tag=gemfire8 .
{code}
Once the image is built, then do the following to start the locator:
{code}
docker run --rm -it \
-e INSTANCE_TYPE=locator \
-e ADDRESS=$(hostname -i) \
-p 10334:10334 \
-p 1099:1099 \
-p 7070:7070 \
-p 47000:47000 \
-p 47001-47100:47001-47100 \
-v /opt/data/gemfire/generic/work:/var/gemfire/work \
-v /opt/data/gemfire/generic/logs:/var/gemfire/logs \
-v /opt/data/gemfire/generic/stats:/var/gemfire/stats \
-v /opt/data/gemfire/generic/conf:/etc/opt/gemfire \
gemfire8 bash
{code}
> gfsh start locator command prints endless dots when starting inside docker
> --------------------------------------------------------------------------
>
> Key: GEODE-1935
> URL: https://issues.apache.org/jira/browse/GEODE-1935
> Project: Geode
> Issue Type: Bug
> Reporter: Abhijat Upadhyay
> Attachments: docker-gemfire8.zip
>
>
> I have built a docker container using gemfire 8.2.1.2. When I try to start
> locator it keeps printing endless dots. I read about this @
> https://discuss.pivotal.io/hc/en-us/articles/223525728-GFSH-hang-issue-when-using-gfsh-start-or-gfsh-status-command
> and thus using gemfire 8.2.1.2. I raised a ticket for Pivotal as well
> https://support.pivotal.io/tickets/38301 but since it is an issue I see
> inside docker, and they do not officially support dockerized gemfire yet, I
> thought I will report it here as well.
> I see that you have containerized gemfire as well on github source repo but
> not sure if you have seen this issue. I can provide you with my source code
> as well if that helps in reproducing this issue.
> Any help/guidance is much appreciated.
> Thank you,
> AU
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
