Closed nshou closed 5 years ago
(Original issue 6 last updated on 2019-09-02T17:13:53.068606+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)
(Original comment by nshou on 2019-01-12T06:36:44.200904+00:00)
The index and data should not have been lost only by stopping/starting the container even without any volume-mounting trick. I've just confirmed by the following commands and it worked well:
#!shell
$ docker run -d -p 9200:9200 -p 5601:5601 nshou/elasticsearch-kibana
0ab0dcb42735ac2a0c002791f64a2eaa1235b351c56f9b43b782a90cc03605ae
$ docker ps -aq
0ab0dcb42735
# Insert a bunch of data...
$ docker stop 0
0
$ docker start 0
0
# Now I can see the inserted data!
I would appreciate it if you could post a series of the command lines and its output to reproduce the issue.
(Original comment by nshou on 2019-09-02T17:13:49.273180+00:00)
I am closing this issue due to inactivity.
(Original issue 6 created by saliniashok on 2018-09-07T07:04:06.521606+00:00)
I used the command sudo docker run -d -p 9200:9200 -p 5601:5601 nshou/elasticsearch-kibana to start
After stopping, the index and data seems loosing. I used the command sudo docker stop