liftbridge/standalone-devWARNING: This container is intended for testing and/or development purposes!
Liftbridge provides lightweight, fault-tolerant message streams by implementing a durable stream augmentation for the NATS messaging system.
This is the source code of the Docker image embedding NATS next to Liftbridge. The image is available on Docker Hub here.
Using the container can be done like this:
$ docker pull liftbridge/standalone-dev $ docker run -d --name=liftbridge-main -p 4222:4222 -p 9292:9292 -p 8222:8222 -p 6222:6222 liftbridge/standalone-dev
This will bootup the container and start both the NATS and Liftbridge servers. We can check the logs to see if the container booted properly:
$ docker logs liftbridge-main [6] 2019/08/21 11:26:09.366043 [INF] Starting nats-server version 2.0.4 [6] 2019/08/21 11:26:09.366094 [INF] Git commit [not set] [6] 2019/08/21 11:26:09.366274 [INF] Starting http monitor on 0.0.0.0:8222 [6] 2019/08/21 11:26:09.366333 [INF] Listening for client connections on 0.0.0.0:4222 [6] 2019/08/21 11:26:09.366354 [INF] Server id is NAI5VLHK3IWC5ENOS3HARMNGZTWNRLXQCYPHTKNXXCGW5EJWR4JXCNVZ [6] 2019/08/21 11:26:09.366358 [INF] Server is ready [6] 2019/08/21 11:26:09.366761 [INF] Listening for route connections on 0.0.0.0:6222 time="2019-08-21 11:26:14" level=info msg="Server ID: MSQaSobS9afF1aN4E8oTIJ" time="2019-08-21 11:26:14" level=info msg="Namespace: liftbridge-default" time="2019-08-21 11:26:14" level=info msg="Retention Policy: [Age: 1 week, Compact: false]" time="2019-08-21 11:26:14" level=info msg="Starting server on :9292..." time="2019-08-21 11:26:15" level=info msg="Server became metadata leader, performing leader promotion actions"
Optionally you can specify the mount point with:
--volume=/tmp/host/liftbridge:/tmp/liftbridge/liftbridge-default
Liftbridge server exposes:
NATS server exposes:
# Client port of 4222 on all interfaces port: 4222 # HTTP monitoring port monitor_port: 8222 # This is for clustering multiple servers together. cluster { # Route connections to be received on any interface on port 6222 port: 6222 # Routes are protected, so need to use them with --routes flag # e.g. --routes=nats-route://ruser:T0pS3cr3t@otherdockerhost:6222 authorization { user: ruser password: T0pS3cr3t timeout: 0.75 } # Routes are actively solicited and connected to from this server. # This Docker image has none by default, but you can pass a # flag to the nats-server docker image to create one to an existing server. routes = [] }
Go to the root directory of the Liftbridge source code and run:
$ make build-dev $ docker build -t liftbridge/standalone-dev -f docker/dev-image/Dockerfile .
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
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 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务