Dear Wazuh Team,
I have been following the instructions provided in your documentation: Wazuh Docker deployment.
On my Ubuntu VirtualBox, the root directory (/) has only 1.5 GB of free space, while the /opt/ directory has 20 GB available. I would like to deploy the Wazuh volumes in /opt/wazuh/volumes instead of the default /var/lib/docker/volumes.After making these changes, I encountered the following issue:
The dashboard displays the message "Wazuh dashboard server is not ready yet" and in the logs, I see:
[ConnectionError]: connect ECONNREFUSED 172.18.0.3:9200.
Could you please advise on how to resolve this issue?
Thank you in advance for your support.
Best regards,
Symeon Zapsis
Hi Symeon,
I just wanted to let you know that the way you have used to specify the mount volumes is not the correct way to do so. This is because Wazuh mounts Docker volumes and in the case you are showing you are doing a mount bind of a directory, which for practical purposes is often the same. Still, it is not, especially in how Docker handles these volumes.
What I recommend you do in case you want to modify the path of the volumes is to create them with local-persist, a Docker plugin that allows you to modify the mount point of the created volumes. To do that you first have to install the plugin on the host machine and then modify the definition of the volumes, which is at the end of the docker-compose.yml file and which in our case has no definition since we let Docker manage it completely.
Here is an example of a definition of the wazuh_etc volume in line 103 for single-node deployment:
wazuh_etc: driver: local-persist driver_opts: mountpoint: /opt/wazuh/volumes/wazuh_etcRemember that you first have to install the plugin to be able to use it.
Please let me know if this helps.