Skip to content

Commit 25fd1af

Browse files
committed
Enhance README with important note on custom configuration file usage in Docker, advising against using 127.0.0.1 in listen directives to prevent connection issues.
Related issue manticoresoftware/manticoresearch#4026
1 parent 16b52f8 commit 25fd1af

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -241,6 +241,8 @@ If you want to run Manticore with a custom configuration that includes table def
241241
docker run --name manticore -v $(pwd)/manticore.conf:/etc/manticoresearch/manticore.conf -v $(pwd)/data/:/var/lib/manticore -p 127.0.0.1:9306:9306 -d manticoresearch/manticore
242242
```
243243

244+
**Important**: When mounting a custom configuration file, avoid using `127.0.0.1:` in the `listen` directives within your configuration file. The container might not have `127.0.0.1` available, which can cause connection issues. Instead, use `0.0.0.0` or omit the IP address entirely. For example, use `listen = 9306:mysql` instead of `listen = 127.0.0.1:9306:mysql`. You can still control external access by binding ports when running the container (e.g., `-p 127.0.0.1:9306:9306`).
245+
244246
Take into account that Manticore search inside the container is run under user `manticore`. Performing operations with table files (like creating or rotating plain tables) should be also done under `manticore`. Otherwise the files will be created under `root` and the search daemon won't have rights to open them. For example here is how you can rotate all tables:
245247

246248
```bash

0 commit comments

Comments
 (0)