Volume Mapping not working

[nhaire41]

I am trying to setup elastalert2. I make changes to existing rules on the LME host. The changes do not reflect in the container. I have tried reloading the daemon and restarting the lme-elastalert.service. Also tried restarting the lme.service. Am I missing something?

[NVivero]

What path are you saving to? The ElastAlert2 container doesn’t automatically pick up edits made on the host. For the container to see your changes, the rules need to live in the host directory that’s mapped into the container. By default, that’s: /opt/lme/config/elastalert2/rules/

A few things to check:

• Make sure you’re editing rules in the mapped directory: sudo ls -l /opt/lme/config/elastalert2/rules/
• If you don’t see your edit reflected in the file’s timestamp/content in that path, make sure you’re editing the copy in that directory, then restart ElastAlert to reload rules: sudo systemctl restart lme-elastalert.service
• After you restart, verify if the changes were picked up: depending on your install, run docker logs lme-elastalert or podman logs lme-elastalert

That should do the trick but let us know if you run into any other issues.

[nhaire41]

I worked on this a bunch last week. I couldn't get any of my changes in the default directory to carry over to the container. I came in this morning, and all was working as intended. I was even able to get my first Kibana test alert to fire off an email. Sorry for the false alarm! Thanks for the assistance, though!