Hey Pierre,
I seriously doubt that your solution is going to work. The elasticsearch.yml
file in the container is not stored in a volume, as far as I understand. This means that your changes will not be persisted from one run to the next.
The “right” solution would be to add the following contents to the docker-compose.override.yml file:
elasticsearch:
environment:
- indices.query.bool.max_clause_count=4096
Then, to take your changes into account, you need to do a full stop/start cycle (yes, painful, I know, but that’s because docker-compose would ignore your changes otherwise) :
tutor local start && tutor local stop # alternatively, you can run 'tutor local reboot'