TheHive-Project / TheHive-Project/Cortex-Analyzers
[Bug] emlparser Image not found: docker.io/cortexneurons/emlparser:2
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 490
- Forks
- 405
- Avg merge
- 2d 43m
- Merged PRs (30d)
- 8
Description
Describe the bug
Trying to run the emlparser to analyze a .eml file and the task fails. I can see in the docker compose logs that it is downloading a container but then at the end it fails.
Error displayed upon failure:
Image not found: docker.io/cortexneurons/emlparser:2
To Reproduce
Steps to reproduce the behavior:
- enable eml parser
- add new analysis
- choose emlparser and upload file
- after it runs, the task fails
Expected behavior
Proper parsing of the eml file is performed.
Complementary information
If applicable, add screenshots and any additional information that might help explain your problem.
Work environment
- Client OS: fedora linux
- Server OS: fedora linux / docker install
- Browse type and version: firefox 118.-0.1 (64-bit)
- Cortex version: 3.1.7-1
- Cortex Analyzer/Responder name: emlparser
- Cortex Analyzer/Responder version: 2.1
Possible solutions
If applicable, indicate possible solutions to the problem.
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with emlparser enabled, following the listed analysis steps and checking the Docker Compose logs. Trace how the analyzer requests docker.io/cortexneurons/emlparser:2 and compare that with the available image configuration. Done means an uploaded .eml file is parsed successfully instead of failing with an image-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100