From fe6afa952bcdc9bca47997ef8d5ffbe191165999 Mon Sep 17 00:00:00 2001 From: "Jonathan A. Sternberg" Date: Mon, 8 Jan 2018 09:16:22 -0600 Subject: [PATCH] Remove mention of the tty exec bug since it no longer exists in supported versions of Docker --- influxdb/content.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/influxdb/content.md b/influxdb/content.md index c589817dd..8d3c944b6 100644 --- a/influxdb/content.md +++ b/influxdb/content.md @@ -124,14 +124,18 @@ Start the container: $ docker run --name=influxdb -d -p 8086:8086 %%IMAGE%% ``` -Run the influx client in another container: +Run the influx client in this container: + +```console +$ docker exec -it influxdb influx +``` + +Or run the influx client in a separate container: ```console $ docker run --rm --link=influxdb -it %%IMAGE%% influx -host influxdb ``` -At the moment, you cannot use `docker exec` to run the influx client since `docker exec` will not properly allocate a TTY. This is due to a current bug in Docker that is detailed in [docker/docker#8755](https://github.com/docker/docker/issues/8755). - ### Database Initialization The InfluxDB image contains some extra functionality for initializing a database. These options are not suggested for production, but are quite useful when running standalone instances for testing.