Estimated reading time: 10 minutes

NATS Streaming is an open-source, high-performance, cloud native messaging streaming system.

GitHub repo:

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Store page for this image at

Supported tags and respective Dockerfile links

Simple Tags

Shared Tags

Quick reference

NATS Streaming: A high-performance cloud native messaging streaming system.


nats-streaming is a high performance streaming server for the NATS Messaging System.

Windows Docker image

Due to restrictions on how the Windows Docker Image is built, running the image without argument will run the NATS Streaming server with memory based store on port 4222 and the monitoring port 8222. If you need to specify any additional argument, or modify these options, you need to specify the executable name as this:

$ docker run nats-streaming-server nats-streaming-server -p 4223 -m 8223

Example usage

# Run a NATS Streaning server
# Each server exposes multiple ports
# 4222 is for clients.
# 8222 is an HTTP management port for information reporting.
# use -p or -P as needed.

$ docker run -d nats-streaming

Output that you would get if you had started with -ti instead of d (for daemon):

[1] 2017/10/25 00:03:04.531435 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.6.0
[1] 2017/10/25 00:03:04.531473 [INF] STREAM: ServerID: ZJHYLl23QGy5nB8VWbggBM
[1] 2017/10/25 00:03:04.531485 [INF] STREAM: Go version: go1.9.1
[1] 2017/10/25 00:03:04.531601 [INF] Starting nats-server version 1.0.4
[1] 2017/10/25 00:03:04.531756 [INF] Starting http monitor on
[1] 2017/10/25 00:03:04.531934 [INF] Listening for client connections on
[1] 2017/10/25 00:03:04.531984 [INF] Server is ready
[1] 2017/10/25 00:03:04.811184 [INF] STREAM: Message store is MEMORY
[1] 2017/10/25 00:03:04.811239 [INF] STREAM: ---------- Store Limits ----------
[1] 2017/10/25 00:03:04.811308 [INF] STREAM: Channels:                  100 *
[1] 2017/10/25 00:03:04.811312 [INF] STREAM: --------- Channels Limits --------
[1] 2017/10/25 00:03:04.811316 [INF] STREAM:   Subscriptions:          1000 *
[1] 2017/10/25 00:03:04.811319 [INF] STREAM:   Messages     :       1000000 *
[1] 2017/10/25 00:03:04.811322 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2017/10/25 00:03:04.811325 [INF] STREAM:   Age          :     unlimited *
[1] 2017/10/25 00:03:04.811328 [INF] STREAM: ----------------------------------

To use a file based store instead, you would run:

$ docker run -d nats-streaming -store file -dir datastore

[1] 2017/10/25 00:03:23.777214 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.6.0
[1] 2017/10/25 00:03:23.777251 [INF] STREAM: ServerID: oLgMEpZtIUGO2O7btAgjDn
[1] 2017/10/25 00:03:23.777254 [INF] STREAM: Go version: go1.9.1
[1] 2017/10/25 00:03:23.777447 [INF] Starting nats-server version 1.0.4
[1] 2017/10/25 00:03:23.777548 [INF] Listening for client connections on
[1] 2017/10/25 00:03:23.777564 [INF] Server is ready
[1] 2017/10/25 00:03:24.062103 [INF] STREAM: Message store is FILE
[1] 2017/10/25 00:03:24.062173 [INF] STREAM: ---------- Store Limits ----------
[1] 2017/10/25 00:03:24.062178 [INF] STREAM: Channels:                  100 *
[1] 2017/10/25 00:03:24.062181 [INF] STREAM: --------- Channels Limits --------
[1] 2017/10/25 00:03:24.062184 [INF] STREAM:   Subscriptions:          1000 *
[1] 2017/10/25 00:03:24.062187 [INF] STREAM:   Messages     :       1000000 *
[1] 2017/10/25 00:03:24.062190 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2017/10/25 00:03:24.062193 [INF] STREAM:   Age          :     unlimited *
[1] 2017/10/25 00:03:24.062196 [INF] STREAM: ----------------------------------

You can also connect to a remote NATS Server running in a docker image. First, run NATS Server:

$ docker run -d --name=nats-main nats

Now, start the Streaming server and link it to the above docker image:

$ docker run -d --link nats-main nats-streaming -store file -dir datastore -ns nats://nats-main:4222

[1] 2017/10/25 00:05:33.454392 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.6.0
[1] 2017/10/25 00:05:33.454430 [INF] STREAM: ServerID: bVCHBZE5wffJriJdvYJxMG
[1] 2017/10/25 00:05:33.454433 [INF] STREAM: Go version: go1.9.1
[1] 2017/10/25 00:05:33.737210 [INF] STREAM: Message store is FILE
[1] 2017/10/25 00:05:33.737262 [INF] STREAM: ---------- Store Limits ----------
[1] 2017/10/25 00:05:33.737267 [INF] STREAM: Channels:                  100 *
[1] 2017/10/25 00:05:33.737298 [INF] STREAM: --------- Channels Limits --------
[1] 2017/10/25 00:05:33.737323 [INF] STREAM:   Subscriptions:          1000 *
[1] 2017/10/25 00:05:33.737327 [INF] STREAM:   Messages     :       1000000 *
[1] 2017/10/25 00:05:33.737330 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2017/10/25 00:05:33.737333 [INF] STREAM:   Age          :     unlimited *
[1] 2017/10/25 00:05:33.737336 [INF] STREAM: ----------------------------------

Notice that the output shows that the NATS Server was not started, as opposed to the first output.

Commandline Options

Streaming Server Options:
    -cid, --cluster_id  <string>     Cluster ID (default: test-cluster)
    -st,  --store <string>           Store type: MEMORY|FILE (default: MEMORY)
          --dir <string>             For FILE store type, this is the root directory
    -mc,  --max_channels <int>       Max number of channels (0 for unlimited)
    -msu, --max_subs <int>           Max number of subscriptions per channel (0 for unlimited)
    -mm,  --max_msgs <int>           Max number of messages per channel (0 for unlimited)
    -mb,  --max_bytes <size>         Max messages total size per channel (0 for unlimited)
    -ma,  --max_age <duration>       Max duration a message can be stored ("0s" for unlimited)
    -ns,  --nats_server <string>     Connect to this external NATS Server URL (embedded otherwise)
    -sc,  --stan_config <string>     Streaming server configuration file
    -hbi, --hb_interval <duration>   Interval at which server sends heartbeat to a client
    -hbt, --hb_timeout <duration>    How long server waits for a heartbeat response
    -hbf, --hb_fail_count <int>      Number of failed heartbeats before server closes the client connection
          --ack_subs <int>           Number of internal subscriptions handling incoming ACKs (0 means one per client's subscription)
          --ft_group <string>        Name of the FT Group. A group can be 2 or more servers with a single active server and all sharing the same datastore.

Streaming Server File Store Options:
    --file_compact_enabled <bool>        Enable file compaction
    --file_compact_frag <int>            File fragmentation threshold for compaction
    --file_compact_interval <int>        Minimum interval (in seconds) between file compactions
    --file_compact_min_size <size>       Minimum file size for compaction
    --file_buffer_size <size>            File buffer size (in bytes)
    --file_crc <bool>                    Enable file CRC-32 checksum
    --file_crc_poly <int>                Polynomial used to make the table used for CRC-32 checksum
    --file_sync <bool>                   Enable File.Sync on Flush
    --file_slice_max_msgs <int>          Maximum number of messages per file slice (subject to channel limits)
    --file_slice_max_bytes <size>        Maximum file slice size - including index file (subject to channel limits)
    --file_slice_max_age <duration>      Maximum file slice duration starting when the first message is stored (subject to channel limits)
    --file_slice_archive_script <string> Path to script to use if you want to archive a file slice being removed
    --file_fds_limit <int>               Store will try to use no more file descriptors than this given limit
    --file_parallel_recovery <int>       On startup, number of channels that can be recovered in parallel

Streaming Server TLS Options:
    -secure <bool>                   Use a TLS connection to the NATS server without
                                     verification; weaker than specifying certificates.
    -tls_client_key <string>         Client key for the streaming server
    -tls_client_cert <string>        Client certificate for the streaming server
    -tls_client_cacert <string>      Client certificate CA for the streaming server

Streaming Server Logging Options:
    -SD, --stan_debug=<bool>         Enable STAN debugging output
    -SV, --stan_trace=<bool>         Trace the raw STAN protocol
    -SDV                             Debug and trace STAN
    (See additional NATS logging options below)

Embedded NATS Server Options:
    -a, --addr <string>              Bind to host address (default:
    -p, --port <int>                 Use port for clients (default: 4222)
    -P, --pid <string>               File to store PID
    -m, --http_port <int>            Use port for http monitoring
    -ms,--https_port <int>           Use port for https monitoring
    -c, --config <string>            Configuration file

Logging Options:
    -l, --log <string>               File to redirect log output
    -T, --logtime=<bool>             Timestamp log entries (default: true)
    -s, --syslog <string>            Enable syslog as log method
    -r, --remote_syslog <string>     Syslog server addr (udp://localhost:514)
    -D, --debug=<bool>               Enable debugging output
    -V, --trace=<bool>               Trace the raw protocol
    -DV                              Debug and trace

Authorization Options:
        --user <string>              User required for connections
        --pass <string>              Password required for connections
        --auth <string>              Authorization token required for connections

TLS Options:
        --tls=<bool>                 Enable TLS, do not verify clients (default: false)
        --tlscert <string>           Server certificate file
        --tlskey <string>            Private key for server certificate
        --tlsverify=<bool>           Enable TLS, verify client certificates
        --tlscacert <string>         Client certificate CA for verification

NATS Clustering Options:
        --routes <string, ...>       Routes to solicit and connect
        --cluster <string>           Cluster URL for solicited routes

Common Options:
    -h, --help                       Show this message
    -v, --version                    Show version
        --help_tls                   TLS help.


Details on how to configure further the NATS Streaming server can be found here

Image Variants

The nats-streaming images come in many flavors, each designed for a specific use case.


This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.


This image is based on Windows Server Core (microsoft/windowsservercore). As such, it only works in places which that image does, such as Windows 10 Professional/Enterprise (Anniversary Edition) or Windows Server 2016.

For information about how to get Docker running on Windows, please see the relevant “Quick Start” guide provided by Microsoft:


View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s nats-streaming/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

library, sample, nats-streaming