![]() ![]() ![]() Reproducible tests: create file docker-compose.yml version: '3. sudo setenforce 0 sudo sed -i 's/SELINUX./SELINUXpermissive/g' /etc/selinux/config. On Rhel-based systems, configure SELinux as below. sudo chmod 775 -R /mnt/datastore sudo chown -R USER:docker /mnt/datastore. ![]() Expected behaviorĮlasticsearch container should start successfully Actual behaviorĮlasticsearch container continually restarts itself InformationįROM /elasticsearch/elasticsearch:6.8. This will create a systemd service named elasticsearch (if your directory is named elasticsearch like /opt/elasticsearch) and enable and start it immediately. If try to start docker image of elasticsearch from docker-compose with sudo and data & log folders do not exist on host or have root permission, the image will fail to start. sudo mkdir /mnt/datastore/setup sudo mkdir /mnt/datastore/elasticsearch. Would it be bad to just modify nf in the docker-desktop distro to set vm.max_map_count = 262144? I have confirmed that modifying that is persistent across restarts. As of 0.9.0, you can specify that a group other than docker should own the Unix socket with the -G option. A new user named elasticsearch and group named elasticsearch is automatically created when we install elasticsearch. When running an elasticsearch container in the WSL2 Tech Preview, the container continually restarts itself complaining "max virtual memory areas vm.max_map_count is too low, increase to at least " The docker daemon must always run as the root user, but if you run the docker client as a user in the docker group then you don't need to add sudo to all the client commands. 12 Answers Sorted by: 29 Elasticsearch can't be run an root user. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |