Open crackytsi opened 4 years ago
BrijJhala
commented
4 years ago True. its really annoying. even I did create Dockerfile using cortex binary and I see this issue. Sounds like they require docker dependency. although its not required. Really I am also awaiting for cortex founder response. Unfortunately no response on their end on any questions.
nadouani
commented
4 years ago Hello @crackytsi can you share the config file?
crackytsi
commented
4 years ago Confg looks like this:
play.http.secret.key="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
MISP {
url=["https://XXXXX"]
key=["YYYYYYYYYYYYYYYYYYYYYYYYYYY"]
certpath=["/opt/Cortex-Analyzers/analyzers/MISP/misp.pem"]
name=["MISP"]
}
search {
index = cortex
uri = "http://127.0.0.1:9200"
}
auth {
provider = [local]
ad {
}
ldap {
}
}
analyzer {
path = ["/opt/Cortex-Analyzers/analyzers"]
fork-join-executor {
parallelism-min = 2
parallelism-factor = 2.0
parallelism-max = 4
}
}
responder {
path = ["/opt/Cortex-Analyzers/responders"]
fork-join-executor {
parallelism-min = 2
parallelism-factor = 2.0
parallelism-max = 4
}
}
hkelley
commented
4 years ago Any news on this? Can it be safely ignored?
8ear
commented
4 years ago Do you start it as Docker container? If yes how looks your docker-compose, or docker commands?
hkelley
commented
4 years ago No, I do not use Docker
rusuvalentin
commented
3 years ago Any updates on this topic?
pandvan
commented
3 years ago Just hit the same issue with Cortex running in a Docker container and making worker to use Docker Engine installed on the host (via bind mounting /var/run/docker.sock.
Why is Cortex trying to connect to unix://localhost:80 socket instead of /var/run/docker.sock?
susangz
commented
2 years ago Hi! Since I'm not running analyzers/responders as dockers, I've tried to set up start_docker environment variable to 0 but they continue appearing. Any news about this? Someone has managed to solve those errors? Thanks!
ferencfresz
commented
1 year ago version: "2"
services:
elasticsearch:
image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9
environment:
- http.host=0.0.0.0
- discovery.type=single-node
ulimits:
nofile:
soft: 65536
hard: 65536
ports:.
- "0.0.0.0:9300:9300"
cortex:
image: thehiveproject/cortex:latest
ports:
- "0.0.0.0:9001:9001"
thehive:
image: thehiveproject/thehive:latest
depends_on:
- elasticsearch
- cortex
ports:
- "0.0.0.0:9000:9000"using UBUNTU 22.04
Request Type
Bug
Work Environment
Problem Description
Cortex failes to start Analyzers (e.g. MISP) with strange error messages. In this setup there is no docker installed and everything comes from local files (classic-mode).
There are some strange warnings about missing cortexutils for python/python3, but it is installed for both python versions.
Is it required to install docker to use Cortex with Cortex 3?
Complementary information
If I directly start cortex as cortex user (for testing purpose only). /opt/cortex/bin/cortex -Dconfig.file=/etc/cortex/application.conf -Dlogger.file=/etc/cortex/logback.xml I can see the following strange errors:
Cortex is started, and correctly working, never the less systemd seems also have a strange status: