You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature description
Include Dockerfile at project level to allow the creation of local Dockerized analyzers
Describe the solution you'd like
In each Analyzer directory, include a Dockerfile specifying the necessary build steps & entry point, with metadata labels.
Additional context
Doing this will be a great step in the direction this blog post was suggesting: moving from process based analyzer execution to docker based.
It will also address a concern myself and other have expressed by the project's use of docker helper scripts rather than the native Docker deployment system.
The text was updated successfully, but these errors were encountered:
I'm back to this issue + pull request. I think that the original requirement makes sense: "Allow the creation of local dockerized analyzers" but there are two issues here:
You have created the Github issue 17 days ago
You have started working on it right away without any discussion/validation with the project team
Let me explain it: Our CI pipeline (a private drone server) builds the docker images automatically (in addition to all the other packages), publish them etc... The docker images it produces contain all the metadata you have added in your script (we use the official docker metadata properties BTW).
We decided to not store the docker files in every analyzer folder.
I support Milesflow's request. I've worked to redo the setup with Drone and was not able to. Really diminish the ability to contribute, test new features easily and trust the project for the long run as I have to trust binary hosted on a 3nd party website.
This is a major concern when wanting to migrate to TheHive/Cortex, contribute and ditch the previous ticket management system.
Feature description
Include Dockerfile at project level to allow the creation of local Dockerized analyzers
Describe the solution you'd like
In each Analyzer directory, include a
Dockerfile
specifying the necessary build steps & entry point, with metadata labels.Additional context
Doing this will be a great step in the direction this blog post was suggesting: moving from process based analyzer execution to docker based.
It will also address a concern myself and other have expressed by the project's use of docker helper scripts rather than the native Docker deployment system.
The text was updated successfully, but these errors were encountered: