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
Find more about configuring InfluxDB [here](https://docs.influxdata.com/influxdb/latest/introduction/installation/)
130
+
Find more about configuring InfluxDB [here](https://docs.influxdata.com/influxdb/latest/introduction/installation/).
131
131
132
132
### Graphite
133
133
@@ -270,6 +270,135 @@ This variant is highly recommended when final image size being as small as possi
270
270
271
271
To minimize image size, it's uncommon for additional related tools (such as `git` or `bash`) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the [`alpine` image description](https://hub.docker.com/_/alpine/) for examples of how to install packages if you are unfamiliar).
272
272
273
+
## `influxdb:data`
274
+
275
+
*This image requires a valid license key from InfluxData.* Please visit our [products page](https://www.influxdata.com/products/) to learn more.
276
+
277
+
This image contains the enterprise data node package for clustering. It supports all of the same options as the OSS image, but it needs port 8088 to be exposed to the meta nodes.
278
+
279
+
Refer to the `influxdb:meta` variant for directions on how to setup a cluster.
280
+
281
+
## `influxdb:meta`
282
+
283
+
*This image requires a valid license key from InfluxData.* Please visit our [products page](https://www.influxdata.com/products/) to learn more.
284
+
285
+
This image contains the enterprise meta node package for clustering. It is meant to be used in conjunction with the `influxdb:data` package of the same version.
286
+
287
+
### Using this Image
288
+
289
+
#### Specifying the license key
290
+
291
+
The license key can be specified using either an environment variable or by overriding the configuration file. If you specify the license key directly, the container needs to be able to access the InfluxData portal.
292
+
293
+
```console
294
+
$ docker run -p 8089:8089 -p 8091:8091 \
295
+
-e INFLUXDB_ENTERPRISE_LICENSE_KEY=<license-key>
296
+
influxdb:meta
297
+
```
298
+
299
+
#### Running the container
300
+
301
+
The examples below will use docker's built-in networking capability. If you use the port exposing feature, the host port and the container port need to be the same.
302
+
303
+
First, create a docker network:
304
+
305
+
```console
306
+
$ docker network create influxdb
307
+
```
308
+
309
+
Start three meta nodes. This is the suggested number of meta nodes. We do not recommend running more or less. If you choose to run more or less, be sure that the number of meta nodes is odd. The hostname must be set on each container to the address that will be used to access the meta node. When using docker networks, the hostname should be made the same as the name of the container.
310
+
311
+
```console
312
+
$ docker run -d --name=influxdb-meta-0 --network=influxdb \
Start the data nodes using `influxdb:data` with similar command line arguments to the meta nodes. You can start as many data nodes as are allowed by your license.
349
+
350
+
```console
351
+
$ docker run -d --name=influxdb-data-0 --network=influxdb \
352
+
-h influxdb-data-0 \
353
+
-e INFLUXDB_LICENSE_KEY=<license-key> \
354
+
influxdb:data
355
+
```
356
+
357
+
You can add `-p 8086:8086` to expose the http port to the host machine. After starting the container, choose one of the meta nodes and add the data node to it.
358
+
359
+
```console
360
+
$ docker exec influxdb-meta-0 \
361
+
influxd-ctl add-data influxdb-data-0:8088
362
+
```
363
+
364
+
Perform these same steps for any other data nodes that you want to add.
365
+
366
+
You can now connect to any of the running data nodes to use your cluster.
367
+
368
+
See the [influxdb](https://hub.docker.com/_/influxdb/) image documentation for more details on how to use the data node images.
369
+
370
+
#### Configuration
371
+
372
+
InfluxDB Meta can be either configured from a config file or using environment variables. To mount a configuration file and use it with the server, you can use this command:
373
+
374
+
Generate the default configuration file:
375
+
376
+
```console
377
+
$ docker run --rm influxdb:meta influxd-meta config > influxdb-meta.conf
378
+
```
379
+
380
+
Modify the default configuration, which will now be available under `$PWD`. Then start the InfluxDB Meta container.
Modify `$PWD` to the directory where you want to store the configuration file.
389
+
390
+
For environment variables, the format is `INFLUXDB_$SECTION_$NAME`. All dashes (`-`) are replaced with underscores (`_`). If the variable isn't in a section, then omit that part.
391
+
392
+
Examples:
393
+
394
+
```console
395
+
INFLUXDB_REPORTING_DISABLED=true
396
+
INFLUXDB_META_DIR=/path/to/metadir
397
+
INFLUXDB_ENTERPRISE_REGISTRATION_ENABLED=true
398
+
```
399
+
400
+
Find more about configuring InfluxDB Meta [here](http://docs.influxdata.com/enterprise_influxdb/latest/production_installation/meta_node_installation/).
401
+
273
402
# License
274
403
275
404
View [license information](https://github.com/influxdata/influxdb/blob/master/LICENSE) for the software contained in this image.
0 commit comments