Persistent data #27
Comments
|
Thanks for the feedback :) Unless you're using the --rm option, the container's filesystem should be persistent. As of Docker 1.2 containers don't auto-restart (by default), so do a Another option is to use the new restart policy option. For example, here's how I start one of my nodes in my cluster to always restart when the Docker daemon starts (such as during host reboot): Regarding If you're still having issues, tell me more about your environment. Since you mentioned running on your laptop, is it a boot2docker setup? |
|
Thanks for those informations. I think the problem is not here: the directories /data and /conf are missing (even after complete Dockerfile reset). Is it possible that there is a permissions problem? My /$ ls -al
total 116
drwxr-xr-x 24 root root 4096 mai 26 09:38 .
drwxr-xr-x 24 root root 4096 mai 26 09:38 ..
drwxr-xr-x 2 root root 12288 mai 19 08:39 bin
drwxr-xr-x 4 root root 4096 mai 19 08:39 boot
drwxr-xr-x 3 root root 4096 avril 27 14:57 build
drwxrwxr-x 2 root root 4096 avril 27 09:02 cdrom
drwxr-xr-x 18 root root 4300 mai 25 16:46 dev
drwxr-xr-x 145 root root 12288 mai 25 09:09 etc
drwxr-xr-x 4 root root 4096 avril 27 14:40 home
lrwxrwxrwx 1 root root 33 mai 6 09:17 initrd.img -> boot/initrd.img-3.19.0-16-generic
lrwxrwxrwx 1 root root 33 avril 27 09:47 initrd.img.old -> boot/initrd.img-3.19.0-15-generic
drwxr-xr-x 24 root root 4096 avril 27 09:45 lib
drwxr-xr-x 2 root root 4096 avril 27 09:42 lib64
drwx------ 2 root root 16384 avril 27 09:00 lost+found
drwxr-xr-x 3 root root 4096 avril 27 09:07 media
drwxr-xr-x 2 root root 4096 oct. 16 2014 mnt
drwxr-xr-x 5 root root 4096 avril 27 10:58 opt
dr-xr-xr-x 255 root root 0 mai 25 09:43 proc
drwx------ 5 root root 4096 mai 25 10:35 root
drwxr-xr-x 27 root root 820 mai 26 09:02 run
drwxr-xr-x 2 root root 12288 mai 19 08:39 sbin
drwxr-xr-x 2 root root 4096 oct. 22 2014 srv
dr-xr-xr-x 13 root root 0 mai 25 12:02 sys
drwxrwxrwt 13 root root 4096 mai 26 09:37 tmp
drwxr-xr-x 10 root root 4096 oct. 22 2014 usr
drwxr-xr-x 14 root root 4096 avril 27 10:38 var
lrwxrwxrwx 1 root root 30 mai 6 09:17 vmlinuz -> boot/vmlinuz-3.19.0-16-generic
lrwxrwxrwx 1 root root 30 avril 27 09:47 vmlinuz.old -> boot/vmlinuz-3.19.0-15-genericI use the Dockerfile on my Ubuntu laptop without boot2docker (official Docker installation) |
|
Excellent, Ubuntu is my primary host platform for using Docker. Can you go through the following sequence, reply with the output from each step and this will help me narrow down the symptoms: |
|
@FPierre , have you been able to try out the latest test case? |
|
Sorry, I'm not able to access to my main computer for another 5 days. I could answer Tuesday |
|
@itzg, sorry I was an another project. Good to me :) |
|
Glad to hear and thanks for following up. |
|
Hello @itzg , thanks for your image ;-) So, I have issue with persist and get logs Have you some idea, how to solutions? Thanks |
|
|
In order to run ES as a non-root user, the container With that said, I'll do some research, because this has always felt awkward to me. |
|
...already found there's healthy demand and discussion about this moby/moby#7198 |
|
@itzg Thanks, now it's ok. |
Hello
I use your awesome Dockerfile Elasticsearch (with Marvel). The only problem is that data are not saved after docker restart (or laptop reboot)
Is there a possibility to save the data to avoid to fill Elasticsearch at every restart ?
I just read the Dockerfile, /data and /conf are not created. There needs to use sudo somewhere?
The text was updated successfully, but these errors were encountered: