ventz
commented
6 years ago @billmurrin I just cloned the repo and made your change (127.0.0.1) and built the image onto clean system (Ubuntu VM) and it works for me without any problems:
# mkdir -p /docker/misp-db# git clone https://github.com/MISP/docker-misp.git
# cd docker-misp
# cat build.sh
#!/bin/bash
docker rmi harvarditsecurity/misp
docker build \
--rm=true --force-rm=true \
--build-arg MYSQL_MISP_PASSWORD=ChangeThisDefaultPassworda9564ebc3289b7a14551baf8ad5ec60a \
--build-arg POSTFIX_RELAY_HOST=localhost \
--build-arg MISP_FQDN=127.0.0.1 \
--build-arg MISP_EMAIL=admin@localhost \
-t harvarditsecurity/misp container
# ./build.sh
(...too long...)
# docker images | grep misp
harvarditsecurity/misp latest 47ca4c2fcff9 8 minutes ago 1.52GB# docker run -it --rm -v /docker/misp-db:/var/lib/mysql harvarditsecurity/misp /init-db
Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
2018-07-07 21:57:05 140201963134080 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-6) starting as process 41 ...
OK
Filling help tables...
2018-07-07 21:57:09 139698537606272 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-6) starting as process 69 ...
OK
Creating OpenGIS required SP-s...
2018-07-07 21:57:12 140677243288704 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-6) starting as process 98 ...
OK
To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system
PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:
'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h f268178a1c0d password 'new-password'
Alternatively you can run:
'/usr/bin/mysql_secure_installation'
which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.
See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.
You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='/var/lib/mysql'
You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl
Please report any problems at http://mariadb.org/jira
The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/
180707 21:57:15 mysqld_safe Logging to syslog.
180707 21:57:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql# docker run -it -d -p 443:443 -p 80:80 -p 3306:3306 -v /docker/misp-db:/var/lib/mysql harvarditsecurity/misp
14fa6979d2f93035ff24d018f2f7ffe432ca3b3b2e2d42e3e0c40f477c3bec85
Just for sanity, I confirmed this on my local system too and it worked there also.
I would suggest taking a look at your environment -- start by cleaning your env and deleting the image ("docker rmi harvarditsecurity/misp"). Then go with the binary first instead of a build ("docker pull harvarditsecurity/misp"). Go through the motions and make sure that runs for you without problems. Confirm the DB initialize successfully before you run the container. If that works, remove it again ("docker rmi harvarditsecurity/misp") and then as a next step clone the github repo and build the default one without any modifications, delete the mysql DB/dir, re-create it + init it, and run that one.
By default the container is set to bind to "localhost", which in this case for all purposes is the same as 127.0.0.1 The reason for this is because $MISP_FQDN is simply used in two places for ServerName, for the permanent redirect to https://$MISP_FQDN, and to configure the baseurl for MISP itself.
Also, check your local containers/services, and make sure nothing else is listening on port tcp/80, tcp/443, tcp/3306 before you run this container.
Another good local debug option is instead of running the container as a service (with -d), instead to run it with an interactive terminal console (with -it) and then manually running the services from the shell/console to see what is failing on your side.
billmurrin
cellango
I'm running the ./build.sh successfully on a Ubuntu box. I am able to run the container. mysql and redis will not start. In my configuration of build.sh, I've changed the FQDN to be 127.0.0.1. I can hit the website on 443, but get a page stating:
When i pull up a bash in the docker image, I don't see mysql or redis running and see the following output in the supervisord output when the container starts: