-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] JSONDecodeError with dockerized analyzers #800
Comments
I found the reason of the problem. In my deployment, Cortex is dockerized, as well as analyzers. So I gave privileges to use docker on the host for the Cortex daemon. When I lauch an analysis, Cortex daemon creates a file in /tmp. Then the analyzer container try to mount /tmp to get this file. My probleme was that the folder /tmp wasn't share between the to containers. So I fixed it by mounting /tmp inside the Cortex container. To improve that, it could be a good idea for the Cortex administrator to choose where to save files to analyze (elsewhere than /tmp). |
Hi @gaglimax !!! Can you please share your configurations please. Thanks in advance |
Hi ! Here is the compose file :
The trick was just to mount /tmp inside the Cortex container, then when you start an analysis, Cortex will create the file to analyze in /tmp. The container created by the analyzer automatically mount /tmp (it's by design), so it can get the file. |
Hi Thanks for sharing. |
The error i have now: Traceback (most recent call last): My docker-compose.yml version: '3.8' |
Describe the bug
There is a JSONDecodeError with cortexneurons analyzers.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The job should succed.
Complementary information
The error is :
This is not about the cortexutils version, because it is 2.0.0.
I tried only with FileInfo_7_0 and EmlParser_1_2, but I think the issue happened on every cortexneurons analyzers.
Work environment
Possible solutions
I think analyzer sontainers are not properly built.
The text was updated successfully, but these errors were encountered: