Remove mention of the tty exec bug since it no longer exists in supported versions of Docker
This commit is contained in:
parent
813ecb9516
commit
fe6afa952b
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Reference in New Issue