Skip to content

Commit ad077a1

Browse files
committed
Merge branch 'release/rel-0.9.0'
2 parents 99a6e09 + 7191fba commit ad077a1

File tree

3 files changed

+20
-51
lines changed

3 files changed

+20
-51
lines changed

Dockerfile

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,6 @@
1-
FROM debian:jessie
1+
FROM java:7-jre
22
MAINTAINER P. Barrett Little <barrett@barrettlittle.com>
33

4-
# Download latest package lists & install dependencies
5-
RUN apt-get update && \
6-
DEBIAN_FRONTEND=noninteractive \
7-
apt-get install -yq \
8-
openjdk-7-jre-headless \
9-
wget
10-
114
# Download version 1.4.2 of logstash
125
RUN cd /tmp && \
136
wget https://download.elasticsearch.org/logstash/logstash/logstash-1.4.2.tar.gz && \

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
NAME = pblittle/docker-logstash
2-
VERSION = 0.8.1
2+
VERSION = 0.9.0
33

44
# Set the LOGSTASH_CONFIG_URL env var to your logstash.conf file.
55
# We will use our basic config if the value is empty.

README.md

Lines changed: 18 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,61 +1,37 @@
1-
# docker-logstash
1+
# logstash
22

3-
This is a highly configurable logstash (1.4.2) image running elasticsearch (1.1.1) and Kibana 3 (3.0.1).
3+
This is a highly configurable logstash (1.4.2) image running Elasticsearch (1.1.1) and Kibana 3 (3.0.1).
44

5-
## Optional, build and run the image from source
6-
7-
If you prefer to build from source rather than use the [pblittle/docker-logstash][1] trusted build published to the public Docker Registry, execute the following:
8-
9-
$ git clone https://github.com/pblittle/docker-logstash.git
10-
$ cd docker-logstash
11-
$ make build
12-
$ make <options> run
13-
14-
See below for a complate example using `Vagrant`.
15-
16-
## Running Logstash
5+
## How to use this image
176

18-
### First, prepare your Logstash configuration file
19-
20-
The logstash configuration file used in this container is downloaded from the internet using `wget`. The configuration file location is determined by the value of the `LOGSTASH_CONFIG_FILE` environment variable, which is set using the `-e` flag when executing `docker run`.
21-
22-
Unless `LOGSTASH_CONFIG_FILE` is overridden, an [example configuration file][2] for an embedded Elasticsearch will be downloaded, moved to `/opt/logstash.conf`, and used in your container.
23-
24-
I have created two reference config files that can be used for testing:
25-
26-
* [Embedded Elasticsearch server](https://gist.githubusercontent.com/pblittle/8778567/raw/logstash.conf) (default)
27-
* [Linked Elasticsearch container](https://gist.githubusercontent.com/pblittle/0b937485fa4a322ea9eb/raw/logstash_linked.conf)
28-
29-
You will find example usage using `-e LOGSTASH_CONFIG_URL=<your_logstash_config_url>` below.
30-
31-
### Second, choose an Elasticsearch install type
32-
33-
To run this logstash image, you have to first choose one of three Elasticsearch configurations.
7+
To run the image, you have to first decide on one of three Elasticsearch configurations:
348

359
* Use the embedded Elasticsearch server
3610
* Use a linked container running Elasticsearch
3711
* Use an external Elasticsearch server
3812

39-
### Use the embedded Elasticsearch server
13+
### Embedded Elasticsearch server
4014

41-
To fetch and start a container running logstash and the embedded Elasticsearch server, simply execute:
15+
To fetch and start a container using an example [logstash.conf][2] and the embedded Elasticsearch server, simply execute:
4216

4317
$ docker run -d \
4418
-p 9292:9292 \
4519
-p 9200:9200 \
4620
pblittle/docker-logstash
4721

48-
If you want to use your own config file rather than the default, don't forget the `LOGSTASH_CONFIG_URL` environment variable as noted above:
22+
By default, an example [logstash.conf][2] will be downloaded using `wget`, moved to `/opt/logstash.conf`, and used in your container.
23+
24+
To use your own config file, set the `LOGSTASH_CONFIG_URL` environment variable using the `-e` flag as follows:
4925

5026
$ docker run -d \
5127
-e LOGSTASH_CONFIG_URL=<your_logstash_config_url> \
5228
-p 9292:9292 \
5329
-p 9200:9200 \
5430
pblittle/docker-logstash
5531

56-
### Use a linked container running Elasticsearch
32+
### Linked container running Elasticsearch
5733

58-
If you want to link to another container running elasticsearch rather than use the embedded server:
34+
If you want to link to container running Elasticsearch rather than use the embedded Elasticsearch server:
5935

6036
$ docker run -d \
6137
-e LOGSTASH_CONFIG_URL=<your_logstash_config_url> \
@@ -64,7 +40,7 @@ If you want to link to another container running elasticsearch rather than use t
6440
-p 9200:9200
6541
pblittle/docker-logstash
6642

67-
To have you the linked elasticsearch container's `bind_host` and `port` automatically detected, you will need to create an `ES_HOST` and `ES_PORT` placeholder in the `elasticsearch` definition in your logstash config file. For example:
43+
To have the linked Elasticsearch container's `bind_host` and `port` automatically detected, you will need to create an `ES_HOST` and `ES_PORT` placeholder in the `elasticsearch` definition in your logstash config file. For example:
6844

6945
output {
7046
elasticsearch {
@@ -73,11 +49,11 @@ To have you the linked elasticsearch container's `bind_host` and `port` automati
7349
}
7450
}
7551

76-
I have created an [example linked config file](https://gist.githubusercontent.com/pblittle/0b937485fa4a322ea9eb/raw/logstash_linked.conf) which includes the `ES_HOST` and `ES_PORT` placeholders described above.
52+
I have created an example [logstash_linked.conf](https://gist.githubusercontent.com/pblittle/0b937485fa4a322ea9eb/raw/logstash_linked.conf) which includes the `ES_HOST` and `ES_PORT` placeholders to serve as an example.
7753

78-
### Use an external Elasticsearch server
54+
### External Elasticsearch server
7955

80-
If you are using an external elasticsearch server rather than the embedded server or a linked container, simply provide a configuration file with the Elasticsearch endpoints already configured:
56+
If you are using an external Elasticsearch server rather than the embedded server or a linked container, simply provide a configuration file with the Elasticsearch endpoints already configured:
8157

8258
$ docker run -d \
8359
-e LOGSTASH_CONFIG_URL=<your_logstash_config_url> \
@@ -91,14 +67,14 @@ You can now verify the logstash installation by visiting the prebuilt logstash d
9167

9268
http://<your_container_ip>:9292/index.html#/dashboard/file/logstash.json
9369

94-
## Test locally using Vagrant
70+
## Optional, build and run the image from source
9571

96-
To build the image locally using Vagrant, you will first need to clone the repository:
72+
If you prefer to build from source rather than use the [pblittle/docker-logstash][1] trusted build published to the public Docker Registry, execute the following:
9773

9874
$ git clone https://github.com/pblittle/docker-logstash.git
9975
$ cd docker-logstash
10076

101-
Start and provision a virtual machine using the provided Vagrantfile:
77+
If you are using Vagrant, start and provision a virtual machine using the provided Vagrantfile:
10278

10379
$ vagrant up
10480
$ vagrant ssh

0 commit comments

Comments
 (0)