docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[nats] Release v1.0.0 

Details can be found [here](https://github.com/nats-io/gnatsd/releases/tag/v1.0.0)
This commit is contained in:
Ivan Kozlovic 2017-07-12 10:59:06 -06:00
parent 18df1af6a1
commit 79df50c549
1 changed files with 14 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
nats/content.md
View File

@ -15,7 +15,7 @@
# use -p or -P as needed. # use -p or -P as needed.
$ docker run -d --name nats-main nats $ docker run -d --name nats-main nats
[INF] Starting nats-server version 0.9.6 [INF] Starting nats-server version 1.0.0
[INF] Starting http monitor on 0.0.0.0:8222 [INF] Starting http monitor on 0.0.0.0:8222
[INF] Listening for client connections on 0.0.0.0:4222 [INF] Listening for client connections on 0.0.0.0:4222
[INF] Server is ready [INF] Server is ready
@ -24,21 +24,24 @@ $ docker run -d --name nats-main nats
... ...
# To run a second server and cluster them together.. # To run a second server and cluster them together..
$ docker run -d --name=nats-2 --link nats-main nats --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 # Note that since you are passing arguments, this overrides the CMD section
# of the Dockerfile, so you need to pass all arguments, including the
# config file.
$ docker run -d --name=nats-2 --link nats-main nats -c gnatsd.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222
# If you want to verify the routes are connected, try # If you want to verify the routes are connected, try this instead:
$ docker run -d --name=nats-2 --link nats-main nats --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV $ docker run -d --name=nats-2 --link nats-main nats -c gnatsd.conf --routes=nats-route://ruser:T0pS3cr3t@nats-main:6222 -DV
[INF] Starting nats-server version 0.9.6 [INF] Starting nats-server version 1.0.0
[DBG] Go build version go1.6.3 [DBG] Go build version go1.7.6
[INF] Starting http monitor on 0.0.0.0:8222 [INF] Starting http monitor on 0.0.0.0:8222
[INF] Listening for client connections on 0.0.0.0:4222 [INF] Listening for client connections on 0.0.0.0:4222
[DBG] Server id is HQLO4vvXi434nlqWjbTbec [DBG] Server id is BEfslG6VOmnIbMQcXTVaVJ
[INF] Server is ready [INF] Server is ready
[INF] Listening for route connections on 0.0.0.0:6222 [INF] Listening for route connections on 0.0.0.0:6222
[DBG] Trying to connect to route on nats-main:6222 [DBG] Trying to connect to route on nats-main:6222
[DBG] 172.17.0.2:6222 - rid:1 - Route connection created [DBG] 172.17.0.2:6222 - rid:1 - Route connection created
[DBG] 172.17.0.2:6222 - rid:1 - Route connect msg sent [DBG] 172.17.0.2:6222 - rid:1 - Route connect msg sent
[DBG] 172.17.0.2:6222 - rid:1 - Registering remote route "PRJPXBdDnqK5ATfyQ7Jjlv" [DBG] 172.17.0.2:6222 - rid:1 - Registering remote route "vay01L4cPxqy75GIDcqKq7"
[DBG] 172.17.0.2:6222 - rid:1 - Route sent local subscriptions [DBG] 172.17.0.2:6222 - rid:1 - Route sent local subscriptions
``` ```
@ -84,11 +87,12 @@ Server Options:
-m, --http_port <port> Use port for http monitoring -m, --http_port <port> Use port for http monitoring
-ms,--https_port <port> Use port for https monitoring -ms,--https_port <port> Use port for https monitoring
-c, --config <file> Configuration file -c, --config <file> Configuration file
-sl,--signal <signal>[=<pid>] Send signal to gnatsd process (stop, quit, reopen, reload)
Logging Options: Logging Options:
-l, --log <file> File to redirect log output -l, --log <file> File to redirect log output
-T, --logtime Timestamp log entries (default: true) -T, --logtime Timestamp log entries (default: true)
-s, --syslog Enable syslog as log method -s, --syslog Log to syslog or windows event log
-r, --remote_syslog <addr> Syslog server addr (udp://localhost:514) -r, --remote_syslog <addr> Syslog server addr (udp://localhost:514)
-D, --debug Enable debugging output -D, --debug Enable debugging output
-V, --trace Trace the raw protocol -V, --trace Trace the raw protocol
@ -110,6 +114,7 @@ Cluster Options:
--routes <rurl-1, rurl-2> Routes to solicit and connect --routes <rurl-1, rurl-2> Routes to solicit and connect
--cluster <cluster-url> Cluster URL for solicited routes --cluster <cluster-url> Cluster URL for solicited routes
--no_advertise <bool> Advertise known cluster IPs to clients --no_advertise <bool> Advertise known cluster IPs to clients
--connect_retries <number> For implicit routes, number of connect retries
Common Options: Common Options: