I am running elasticsearch from within a docker container.
While configuring elasticsearch for ssl and shield my elasticsearch.yml
file got illegal entry i
replace it without losing data
Ideally, those data should be stored in path mounted from separate data volume containers (which do not run, they are just created). That way, your main service container (the elasticsearch
one) can crash and be replaced at will.
In that configuration (mounting data from volume containers), you could rebuild your elasticsearch
image with the new config file, and resume from there.
In your current config, if those data are not in a VOLUME declared by your Dockerfile, what you can do is:
[docker commit ][1] newimage