专属域名
文档搜索
轩辕助手
Run助手
邀请有礼
返回顶部
快速返回页面顶部
收起
收起工具栏
轩辕镜像 官方专业版
轩辕镜像 官方专业版轩辕镜像 官方专业版官方专业版
首页个人中心搜索镜像

交易
充值流量我的订单
工具
提交工单镜像收录一键安装
Npm 源Pip 源Homebrew 源
帮助
常见问题
其他
关于我们网站地图

官方QQ群: 1072982923

arm32v6/nats-streaming Docker 镜像 - 轩辕镜像

nats-streaming
arm32v6/nats-streaming
DEPRECATED; An open-source, high-performance, cloud native messaging streaming system.
0 次下载
🚀 生产环境还在裸拉官方镜像?一次故障=一次通宵
镜像简介版本下载
🚀 生产环境还在裸拉官方镜像?一次故障=一次通宵

DEPRECATION NOTICE

The NATS Streaming Server is being deprecated. Critical bug fixes and security fixes will be applied until June of 2023. NATS enabled applications requiring persistence should use JetStream.

Quick reference

  • Maintained by:
    the NATS Project

  • Where to get help:
    the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow

Supported tags and respective Dockerfile links

No supported tags

Quick reference (cont.)

  • Where to file issues:
    [***]

  • Supported architectures: (more info)
    No supported architectures

  • Published image artifact details:
    repo-info repo's repos/nats-streaming/ directory (history)
    (image metadata, transfer size, etc)

  • Image updates:
    official-images repo's library/nats-streaming label
    official-images repo's library/nats-streaming file (history)

  • Source of this description:
    docs repo's nats-streaming/ directory (history)

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

!logo

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

Backward compatibility note

Note that the Streaming server itself is backward compatible with previous releases, however, v0.15.0+ now embeds a NATS Server 2.0, which means that if you run with the embedded NATS server and want to route it to your existing v0.14.3- servers, it will fail due to NATS Server routing protocol change. You can however use v0.15.0+ and connect it to existing NATS cluster and therefore have a mix of v0.15.0 and v0.14.3- streaming servers.

Windows Docker images

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:

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

If you need to specify the entrypoint:

bash
$ docker run --entrypoint c:/nats-streaming-server/nats-streaming-server -p 4222:4222 -p 8222:8222 nats-streaming

Non Windows Docker images

If you need to provide arguments to the NATS Streaming server, just pass them to the command line. For instance, to change the listen and monitoring port to 4223 and 8223 respectively:

bash
$ docker run -p 4223:4223 -p 8223:8223 nats-streaming -p 4223 -m 8223

If you need to specify the entrypoint:

bash
$ docker run --entrypoint /nats-streaming-server -p 4222:4222 -p 8222:8222 nats-streaming

Example usage

bash
# Run a NATS Streaming server
# Each server exposes multiple ports
# 4222 is for clients.
# 8222 is an HTTP management port for information reporting.
#
# To actually publish the ports when running the container, use the Docker port mapping
# flag "docker run -p <hostport>:<containerport>" to publish and map one or more ports,
# or the -P flag to publish all exposed ports and map them to high-order ports.
#
# This should not be confused with the NATS Streaming Server own -p parameter.
# For instance, to run the NATS Streaming Server and have it listen on port 4444,
# you would have to run like this:
#
#   docker run -p 4444:4444 nats-streaming -p 4444
#
# Or, if you want to publish the port 4444 as a different port, for example 5555:
#
#   docker run -p 5555:4444 nats-streaming -p 4444
#
# Check "docker run" for more information.

$ docker run -d -p 4222:4222 -p 8222:8222 nats-streaming

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

bash
[1] 2022/10/11 14:57:50.404688 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.25.2
[1] 2022/10/11 14:57:50.404739 [INF] STREAM: ServerID: fbZJjwGYLBpNM5I8z23NSN
[1] 2022/10/11 14:57:50.404741 [INF] STREAM: Go version: go1.19.2
[1] 2022/10/11 14:57:50.404743 [INF] STREAM: Git commit: [9e599667]
[1] 2022/10/11 14:57:50.406004 [INF] Starting nats-server
[1] 2022/10/11 14:57:50.406009 [INF]   Version:  2.9.3
[1] 2022/10/11 14:57:50.406011 [INF]   Git:      [25e82d7]
[1] 2022/10/11 14:57:50.406013 [INF]   Name:     NDQOBTB34ECZWAKAJAREPEXQPXGKUEJEZINCHV2CIHGGJQCSCVPQPU5W
[1] 2022/10/11 14:57:50.406015 [INF]   ID:       NDQOBTB34ECZWAKAJAREPEXQPXGKUEJEZINCHV2CIHGGJQCSCVPQPU5W
[1] 2022/10/11 14:57:50.406423 [INF] Listening for client connections on 0.0.0.0:4222
[1] 2022/10/11 14:57:50.406679 [INF] Server is ready
[1] 2022/10/11 14:57:50.434935 [INF] STREAM: Recovering the state...
[1] 2022/10/11 14:57:50.434945 [INF] STREAM: No recovered state
[1] 2022/10/11 14:57:50.435271 [INF] STREAM: Message store is MEMORY
[1] 2022/10/11 14:57:50.435303 [INF] STREAM: ---------- Store Limits ----------
[1] 2022/10/11 14:57:50.435306 [INF] STREAM: Channels:                  100 *
[1] 2022/10/11 14:57:50.435308 [INF] STREAM: --------- Channels Limits --------
[1] 2022/10/11 14:57:50.435310 [INF] STREAM:   Subscriptions:          1000 *
[1] 2022/10/11 14:57:50.435311 [INF] STREAM:   Messages     :       *** *
[1] 2022/10/11 14:57:50.435313 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2022/10/11 14:57:50.435315 [INF] STREAM:   Age          :     unlimited *
[1] 2022/10/11 14:57:50.435316 [INF] STREAM:   Inactivity   :     unlimited *
[1] 2022/10/11 14:57:50.435318 [INF] STREAM: ----------------------------------
[1] 2022/10/11 14:57:50.435320 [INF] STREAM: Streaming Server is ready

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

bash
$ docker run -d -p 4222:4222 -p 8222:8222 nats-streaming -store file -dir datastore

[1] 2022/10/11 14:59:45.818823 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.25.2
[1] 2022/10/11 14:59:45.818874 [INF] STREAM: ServerID: mNhpLEpCO6WFqrnD9CYEZa
[1] 2022/10/11 14:59:45.818876 [INF] STREAM: Go version: go1.19.2
[1] 2022/10/11 14:59:45.818877 [INF] STREAM: Git commit: [9e599667]
[1] 2022/10/11 14:59:45.820192 [INF] Starting nats-server
[1] 2022/10/11 14:59:45.820196 [INF]   Version:  2.9.3
[1] 2022/10/11 14:59:45.820198 [INF]   Git:      [25e82d7]
[1] 2022/10/11 14:59:45.820200 [INF]   Name:     NCDMFFEVOSPVVGQZVEQ3O5434LHF2KAPOR5LKAI7YEIAFIABTHQLZRLA
[1] 2022/10/11 14:59:45.820202 [INF]   ID:       NCDMFFEVOSPVVGQZVEQ3O5434LHF2KAPOR5LKAI7YEIAFIABTHQLZRLA
[1] 2022/10/11 14:59:45.820688 [INF] Listening for client connections on 0.0.0.0:4222
[1] 2022/10/11 14:59:45.820849 [INF] Server is ready
[1] 2022/10/11 14:59:45.848443 [INF] STREAM: Recovering the state...
[1] 2022/10/11 14:59:45.848737 [INF] STREAM: No recovered state
[1] 2022/10/11 14:59:45.849050 [INF] STREAM: Message store is FILE
[1] 2022/10/11 14:59:45.849054 [INF] STREAM: Store location: datastore
[1] 2022/10/11 14:59:45.849070 [INF] STREAM: ---------- Store Limits ----------
[1] 2022/10/11 14:59:45.849072 [INF] STREAM: Channels:                  100 *
[1] 2022/10/11 14:59:45.849073 [INF] STREAM: --------- Channels Limits --------
[1] 2022/10/11 14:59:45.849075 [INF] STREAM:   Subscriptions:          1000 *
[1] 2022/10/11 14:59:45.849076 [INF] STREAM:   Messages     :       *** *
[1] 2022/10/11 14:59:45.849077 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2022/10/11 14:59:45.849078 [INF] STREAM:   Age          :     unlimited *
[1] 2022/10/11 14:59:45.849079 [INF] STREAM:   Inactivity   :     unlimited *
[1] 2022/10/11 14:59:45.849080 [INF] STREAM: ----------------------------------
[1] 2022/10/11 14:59:45.849082 [INF] STREAM: Streaming Server is ready

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

bash
$ docker run -d --name=nats-main -p 4222:4222 -p 6222:6222 -p 8222:8222 nats

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

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

[1] 2022/10/11 15:00:56.780184 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.25.2
[1] 2022/10/11 15:00:56.780235 [INF] STREAM: ServerID: jVQkB4KiIN4IVIuVoSumE0
[1] 2022/10/11 15:00:56.780237 [INF] STREAM: Go version: go1.19.2
[1] 2022/10/11 15:00:56.780241 [INF] STREAM: Git commit: [9e599667]
[1] 2022/10/11 15:00:56.809173 [INF] STREAM: Recovering the state...
[1] 2022/10/11 15:00:56.810336 [INF] STREAM: Recovered 0 channel(s)
[1] 2022/10/11 15:00:56.810612 [INF] STREAM: Message store is FILE
[1] 2022/10/11 15:00:56.810617 [INF] STREAM: Store location: datastore
[1] 2022/10/11 15:00:56.810633 [INF] STREAM: ---------- Store Limits ----------
[1] 2022/10/11 15:00:56.810635 [INF] STREAM: Channels:                  100 *
[1] 2022/10/11 15:00:56.810636 [INF] STREAM: --------- Channels Limits --------
[1] 2022/10/11 15:00:56.810637 [INF] STREAM:   Subscriptions:          1000 *
[1] 2022/10/11 15:00:56.810639 [INF] STREAM:   Messages     :       *** *
[1] 2022/10/11 15:00:56.810640 [INF] STREAM:   Bytes        :     976.56 MB *
[1] 2022/10/11 15:00:56.810641 [INF] STREAM:   Age          :     unlimited *
[1] 2022/10/11 15:00:56.810642 [INF] STREAM:   Inactivity   :     unlimited *
[1] 2022/10/11 15:00:56.810643 [INF] STREAM: ----------------------------------
[1] 2022/10/11 15:00:56.810644 [INF] STREAM: Streaming Server is ready

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

Commandline Options

bash
Streaming Server Options:
    -cid, --cluster_id  <string>         Cluster ID (default: test-cluster)
    -st,  --store <string>               Store type: MEMORY|FILE|SQL (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)
    -mi,  --max_inactivity <duration>    Max inactivity (no new message, no subscription) after which a channel can be garbage collected (0 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
          --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
    -sl,  --signal <signal>[=<pid>]      Send signal to nats-streaming-server process (stop, quit, reopen, reload - only for embedded NATS Server)
          --encrypt <bool>               Specify if server should use encryption at rest
          --encryption_cipher <string>   Cipher to use for encryption. Currently support AES and CHAHA (ChaChaPoly). Defaults to AES
          --encryption_key <string>      Encryption Key. It is recommended to specify it through the NATS_STREAMING_ENCRYPTION_KEY environment variable instead
          --replace_durable <bool>       Replace the existing durable subscription instead of reporting a duplicate durable error

Streaming Server Clustering Options:
    --clustered <bool>                     Run the server in a clustered configuration (default: false)
    --cluster_node_id <string>             ID of the node within the cluster if there is no stored ID (default: random UUID)
    --cluster_bootstrap <bool>             Bootstrap the cluster if there is no existing state by electing self as leader (default: false)
    --cluster_peers <string, ...>          Comma separated list of cluster peer node IDs to bootstrap cluster state
    --cluster_log_path <string>            Directory to store log replication data
    --cluster_log_cache_size <int>         Number of log entries to cache in memory to reduce disk IO (default: 512)
    --cluster_log_snapshots <int>          Number of log snapshots to retain (default: 2)
    --cluster_trailing_logs <int>          Number of log entries to leave after a snapshot and compaction
    --cluster_sync <bool>                  Do a file sync after every write to the replication log and message store
    --cluster_raft_logging <bool>          Enable logging from the Raft library (disabled by default)
    --cluster_allow_add_remove_node <bool> Enable the ability to send NATS requests to the leader to add/remove cluster nodes

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
    --file_truncate_bad_eof <bool>       Truncate files for which there is an unexpected EOF on recovery, dataloss may occur
    --file_read_buffer_size <size>       Size of messages read ahead buffer (0 to disable)
    --file_auto_sync <duration>          Interval at which the store should be automatically flushed and sync'ed on disk (<= 0 to disable)

Streaming Server SQL Store Options:
    --sql_driver <string>            Name of the SQL Driver ("mysql" or "postgres")
    --sql_source <string>            Datasource used when opening an SQL connection to the database
    --sql_no_caching <bool>          Enable/Disable caching for improved performance
    --sql_max_open_conns <int>       Maximum number of opened connections to the database
    --sql_bulk_insert_limit <int>    Maximum number of messages stored with a single SQL "INSERT" statement

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
         --syslog_name               On Windows, when running several servers as a service, use this name for the event source
    (See additional NATS logging options below)

Embedded NATS Server Options:
    -a, --addr <string>              Bind to host address (default: 0.0.0.0)
    -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 <bool>              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.

Configuration

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

License

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.

查看更多 nats-streaming 相关镜像 →
nats-streaming logo
nats-streaming
已废弃;一个开源、高性能、云原生的消息流系统。
166100M+ pulls
上次更新:未知
winamd64/nats-streaming logo
winamd64/nats-streaming
DEPRECATED; An open-source, high-performance, cloud native messaging streaming system.
100K+ pulls
上次更新:未知
arm32v7/nats-streaming logo
arm32v7/nats-streaming
已废弃的开源高性能云原生消息流系统。
100K+ pulls
上次更新:未知
arm64v8/nats-streaming logo
arm64v8/nats-streaming
已弃用;一个开源、高性能的云原生消息流系统。
100K+ pulls
上次更新:未知
amd64/nats-streaming logo
amd64/nats-streaming
DEPRECATED; An open-source, high-performance, cloud native messaging streaming system.
100K+ pulls
上次更新:未知

轩辕镜像配置手册

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式

登录仓库拉取

通过 Docker 登录认证访问私有仓库

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

Docker Compose

Docker Compose 项目配置

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

MacOS OrbStack

MacOS OrbStack 容器配置

宝塔面板

在宝塔面板一键配置镜像

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

极空间

极空间 NAS 系统配置服务

爱快路由

爱快 iKuai 路由系统配置

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

专属域名拉取

无需登录使用专属域名

需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单

镜像拉取常见问题

轩辕镜像免费版与专业版有什么区别?

免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。

轩辕镜像支持哪些镜像仓库?

专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。

流量耗尽错误提示

当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。

410 错误问题

通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。

manifest unknown 错误

先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。

镜像拉取成功后,如何去掉轩辕镜像域名前缀?

使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。

查看全部问题→

用户好评

来自真实用户的反馈,见证轩辕镜像的优质服务

用户头像

oldzhang

运维工程师

Linux服务器

5

"Docker访问体验非常流畅,大镜像也能快速完成下载。"

轩辕镜像
镜像详情
...
arm32v6/nats-streaming
官方博客Docker 镜像使用技巧与技术博客
热门镜像查看热门 Docker 镜像推荐
一键安装一键安装 Docker 并配置镜像源
咨询镜像拉取问题请 提交工单,官方技术交流群:1072982923
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
咨询镜像拉取问题请提交工单,官方技术交流群:
轩辕镜像面向开发者与科研用户,提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库,本站不存储、不修改、不传播任何镜像内容。
官方邮箱:点击复制邮箱
©2024-2026 源码跳动
官方邮箱:点击复制邮箱Copyright © 2024-2026 杭州源码跳动科技有限公司. All rights reserved.