MISP
/
misp-docker
mirror of https://github.com/MISP/misp-docker
2
0
Fork 0
Code Issues Releases Wiki Activity
MISP Docker (XME edition)
108 Commits
2 Branches
0 Tags
1.4 MiB
Shell 73.8%
Dockerfile 22.1%
HCL 4%
 
 
 
Go to file
Jason Kendall 3a55ba7847 Update readme for new docker-compose 2020-02-27 19:53:47 -05:00
modules Split Core and Modules version args - fixes #36 2020-02-27 16:15:22 -05:00
server Fix some order of operations 2020-02-27 18:14:59 -05:00
server-configs Use distributed configs for defaults 2020-02-27 18:10:39 -05:00
.env Bump MISP Core version 2020-02-27 16:18:15 -05:00
.gitignore Cleanup gitignore 2020-02-27 18:39:54 -05:00
.travis.yml Split docker-compose and build-docker-compose 2020-02-27 19:50:42 -05:00
LICENSE Create LICENSE 2020-01-29 10:29:24 -05:00
README.md Update readme for new docker-compose 2020-02-27 19:53:47 -05:00
build-docker-compose.yml Split docker-compose and build-docker-compose 2020-02-27 19:50:42 -05:00
docker-compose.yml Split docker-compose and build-docker-compose 2020-02-27 19:50:42 -05:00

README.md

CoolAcid's MISP Docker images

Codacy Badge CodeFactor Build Status Gitter chat

A (nearly) production ready Dockered MISP

This is based on some of the work from the DSCO docker build, nearly all of the details have been rewritten.

  • Components are split out where possible, currently this is only the MISP modules
  • Over writable configuration files
  • Allows volumes for file store
  • Cron job runs updates, pushes, and pulls - Logs go to docker logs
  • Docker-Compose uses off the shelf images for Redis and MySQL
  • Images directly from docker hub, no build required
  • Slimmed down images by using build stages and slim parent image, removes unnecessary files from images

Docker Tags

Docker hub builds the images automatically based on git tags. I try and tag using the following details

v[MISP Version][Our build version]

  • MISP version is the MISP tag we're building
  • Our build version is the iteration for our changes with the same MISP version

Getting Started

Development/Test

  • Grab the docker-compose.yml and server-configs/email.php files (Keep directory structure)

  • A dry run will create sane default configurations

  • docker-compose up

  • Login to https://localhost

    • User: admin@admin.test
    • Password: admin

  • Profit

Using the image for development

Pull the entire repository, you can build the images using docker-compose -f docker-compose.yml -f build-docker-compose.yml build

Once you have the docker container up you can access the container by running docker-compose exec misp /bin/bash. This will provide you with a root shell. You can use apt update and then install any tools you wish to use. Finally, copy any changes you make outside of the container for commiting to your branch. git diff -- [dir with changes] could be used to reduce the number of changes in a patch file, however, becareful when using the git diff command.

Production

  • Use docker-compose, or some other config management tool

  • Directory volume mount SSL Certs ./ssl: /etc/ssl/certs

    • Certificate File: cert.pem
    • Certificate Key File: key.pem

  • Directory volume mount and create configs: /var/www/MISP/app/Config/

  • Additional directory volume mounts:

    • /var/www/MISP/app/files
    • /var/www/MISP/.gnupg
    • /var/www/MISP/.smime

Image file sizes

  • Core server(Saved: 2.5GB)

    • Original Image: 3.17GB
    • First attempt: 2.24GB
    • Remove chown: 1.56GB
    • PreBuild python modules, and only pull submodules we need: 800MB
    • PreBuild PHP modules: 664MB

  • Modules (Saved: 640MB)

    • Original: 1.36GB
    • Pre-build modules: 750MB