Segmentation fault using parsers in Docker #71
-
Hi, I've made a small script that does nothing more basically than |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
Hi, We discovered a conflict with llmware and the latest version of the mongoc driver that was released 2 days ago and this can cause a segmentation fault. To see if this is what you are encountering, please downgrade the mongo-c-driver to v1.24. Or we'll be releasing an llmware update today that addresses the issue. Or, if you share your docker file, we can take a look to see what else might be happening. |
Beta Was this translation helpful? Give feedback.
-
Hi @JessBerl, thanks for your fast response. Good to hear that it's actually something that's broken, can you let me know/indicate here when a fixed version is released and the corresponding version nr? This is the docker file I use which produces the error:
|
Beta Was this translation helpful? Give feedback.
-
Hi @hawkeye-bot Thanks for trying us out and the feedback! The issue in this case, is that setting the ulimit in the Dockerfile is not sufficient and it needs to be set when running the container. I've attached a complete working example, but the key part is the --ulimit setting you'll see in docker-run.sh:
With that set the parsing can succeed:
|
Beta Was this translation helpful? Give feedback.
-
Thanks a lot @turnham , I can confirm this solves my issue. Might be good to take this up on the readme file where the ulimit is mentioned that this is the way to do it for docker |
Beta Was this translation helpful? Give feedback.
Hi @hawkeye-bot Thanks for trying us out and the feedback! The issue in this case, is that setting the ulimit in the Dockerfile is not sufficient and it needs to be set when running the container. I've attached a complete working example, but the key part is the --ulimit setting you'll see in docker-run.sh:
With that set the parsing can succeed: