You need a recent docker version installed, take a look here for instructions.
This will create a container with all Graylog services running:
$ docker pull graylog2/allinone $ docker run -t -p 9000:9000 -p 12201:12201 -p 12201:12201/udp graylog2/allinone
To run the container in the background replace -t with -d.
Using the beta container¶
You can also run a pre-release or beta version of Graylog using Docker. The pre-releases are included in the graylog2/server image. Follow this guide and pick a alpha/beta tag like:
$ docker run --link some-mongo:mongo --link some-elasticsearch:elasticsearch -d graylog-server:2.0.0-beta.1-1
We only recommend to run beta versions if you are an experienced Graylog user and know what you are doing.
After starting the container, your Graylog instance is ready to use. You can reach the web interface by pointing your browser to the IP address of your Docker host: http://<host IP>:9000
The default login is Username: admin, Password: admin.
How to get log data in¶
You can create different kinds of inputs under System -> Inputs, however you can only use ports that have been properly mapped to your docker container, otherwise data will not get through. You already exposed the default GELF port 12201, so it is a good idea to start a GELF TCP input there.
To start another input you have to expose the right port e.g. to start a raw TCP input on port 5555; stop your container and recreate it, whilst appending -p 5555:5555 to your run argument. Similarly, the same can be done for UDP by appending -p 5555:5555/udp option. Then you can send raw text to Graylog like echo ‘first log message’ | nc localhost 5555
You can configure the most important aspects of your Graylog instance through environment variables. In order to set a variable add a -e VARIABLE_NAME option to your docker run command. For example to set another admin password start your container like this:
$ docker run -t -p 9000:9000 -p 12201:12201 -p 12201:12201/udp -e GRAYLOG_PASSWORD=SeCuRePwD graylog2/allinone
|Variable Name||Configuration Option|
|GRAYLOG_PASSWORD||Set admin password|
|GRAYLOG_USERNAME||Set username for admin user (default: admin)|
|GRAYLOG_TIMEZONE||Set timezone (TZ) you are in|
|GRAYLOG_SMTP_SERVER||Hostname/IP address of your SMTP server for sending alert mails|
|GRAYLOG_RETENTION||Configure how long or how many logs should be stored|
|GRAYLOG_NODE_ID||Set server node ID (default: random)|
|GRAYLOG_SERVER_SECRET||Set salt for encryption|
|GRAYLOG_MASTER||IP address of a remote master container (see multi container setup)|
|GRAYLOG_SERVER||Run only server components|
|GRAYLOG_WEB||Run web interface only|
|ES_MEMORY||Set memory used by Elasticsearch (syntax: 1024m). Defaults to 60% of host memory|
Set an admin password:
Change admin username:
Set your local timezone:
Set a SMTP server for alert e-mails:
Disable TLS/SSL for mail delivery:
GRAYLOG_SMTP_SERVER="mailserver.com --no-tls --no-ssl"
Set SMTP server with port, authentication, backlink URL and changed sender address:
Set a static server node ID:
Set a configuration master for linking multiple containers:
Only start server services:
Only run web interface:
Keep 30Gb of logs, distributed across 10 Elasticsearch indices:
Keep one month of logs, distributed across 30 indices with 24 hours of logs each:
Limit amount of memory Elasticsearch is using:
In order to persist log data and configuration settings mount the Graylog data directory outside the container:
$ docker run -t -p 9000:9000 -p 12201:12201 -p 12201:12201/udp -e GRAYLOG_NODE_ID=some-rand-omeu-uidasnodeid -e GRAYLOG_SERVER_SECRET=somesecretsaltstring -v /graylog/data:/var/opt/graylog/data -v /graylog/logs:/var/log/graylog graylog2/allinone
Please make sure that you always use the same node-ID and server secret. Otherwise your users can’t login or inputs will not be started after creating a new container on old data.
Other volumes to persist:
|/var/opt/graylog/data||Elasticsearch for raw log data and MongoDB as configuration store|
|/var/log/graylog||Internal logs for all running services|
|/opt/graylog/plugin||Graylog server plugins|
Multi container setup¶
The Omnibus package used for creating the container is able to split Graylog into several components. This works in a Docker environment as long as your containers run on the same hardware respectively the containers need to have direct network access between each other. The first started container is the so called master, other containers can grab configuration options from here.
To setup two containers, one for the web interface and one for the server component do the following:
Start the master with Graylog server parts:
$ docker run -t -p 12900:12900 -p 12201:12201 -p 12201:12201/udp -p 4001:4001 -e GRAYLOG_SERVER=true graylog2/allinone
The configuration port 4001 is now accessible through the host IP address.
Start the web interface in a second container and give the host address as master to fetch configuration options:
$ docker run -t -p 9000:9000 -e GRAYLOG_MASTER=<host IP address> -e GRAYLOG_WEB=true graylog2/allinone
Graylog comes with a pre-configured SSL configuration. On start-up time a self-signed certificate is generated and used on port 443 to provide the web interface via HTTPS. Simply expose the port like this:
$ docker run -t -p 443:443 graylog2/allinone
It is also possible to swap the certificate with your own files. To achieve this mount the CA directory to the Docker host:
$ docker run -t -p 443:443 -v /somepath/ca:/opt/graylog/conf/nginx/ca graylog2/allinone
If you put a file called /somepath/ca/graylog.crt respectively /somepath/ca/graylog.key in place before starting the container, Graylog will pick up those files and make use of your own certificate.
In case you see warnings regarding open file limit, try to set ulimit from the outside of the container:
$ docker run --ulimit nofile=64000:64000 ...
The devicemapper storage driver can produce problems with Graylogs disk journal on some systems. In this case please pick another driver like aufs or overlay. Have a look here
To build the image from scratch run:
$ docker build -t graylog .