Interacting with container (attach) to add existing data to data folder

[Analect]

Hi. Thanks for setting this up.
I've been running your container using:
docker run -d -p 9200:9200 -p 9300:9300 dockerfile/elasticsearch

However, when I attach to the container, I have no prompt or ability to interact with the container, such as copying across an existing dataset to the data folder within the container. I experimented with removing the -d and using -i and -t settings thinking that might drop me into the filesystem when I attach, but that just causes errors such as:

docker run -name=elasticsearch -i -t -p 9200:9200 -p 9300:9300 dockerfile/elasticsearch bin/bash
log4j:WARN No appenders could be found for logger (node).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

Any suggestions on what the right form of the run command should include to give me this ability to interact with the ES container once running?

Thanks.

[pilwon]

@Analect It's possible that the image is broken with the recent updates. We accept pull requests. If you find a solution, please share with us.

[shreyaskarnik]

@Analect This script has a entrypoint which makes your docker containers behave like a binary. More details on http://crosbymichael.com/dockerfile-best-practices.html also check http://docs.docker.io/en/latest/reference/run/ also tl;dr docker run -i -t -entrypoint /bin/bash dockerfile/elasticsearch -c bash this is what you need to execute to drop in the shell for that container. Also submitting a PR to remove the log warnings. cc @pilwon

[Analect]

@shreyu86 Thanks for your input.

[Analect]

@shreyu86
I just notice an updated version of the best-practices published y'day.
http://crosbymichael.com/dockerfile-best-practices-take-2.html

[pilwon]

Merged #3

[hamiltont]

@Analect see https://github.com/jpetazzo/nsenter for future reference. You can launch the container and then attach into it with a standard shell