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

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

官方QQ群: 1072982923

modelrockettier/corosync-qnetd Docker 镜像 - 轩辕镜像

corosync-qnetd
modelrockettier/corosync-qnetd
modelrockettier
Proxmox Corosync QNet Daemon
4 收藏0 次下载
😎 镜像稳了,发布才敢点回车
镜像简介版本下载
😎 镜像稳了,发布才敢点回车

Dockerized Corosync QNet Daemon

Sets up a Corosync v3 QNet Daemon for use with Proxmox v6.

[]([***]

This allows you to deploy an external voter on a server that is not running Proxmox (e.g. a NAS). The external voter mainly serves to break ties (e.g. if the cluster has an even number of nodes).

See <[***]> for more information.

NOTE: This container does not have an SSH server installed, so setting it up is a bit more involved than a simple pvecm qdevice setup.

Getting Started

Prerequisites

This assumes that you have at least 2 Proxmox nodes and a separate docker server.

You will also need to set a few environment variables (or manually replace them with the appropriate values in the commands below):

  • CLUSTER_NAME: The name of your Proxmox cluster (must match the cluster_name key in /etc/corosync/corosync.conf on your Proxmox nodes.

    E.g.

    CLUSTER_NAME=cluster1
    
  • PROXMOX_NODE: The credentials to ssh into your first Proxmox node (usually user@host or user@ip).

    E.g.

    PROXMOX_NODE=root@proxmox1
    
  • QNETD_DATA: Where to store the corosync-qnetd config data on the docker host.

    E.g.

    QNETD_DATA=/etc/corosync-data
    
Instructions

The general flow is to set up the qnet device with 1 Proxmox node, then to add the rest of the Proxmox nodes afterwards.

You will need to run some commands on the docker host and some on the initial Proxmox node. Instructions below are prefixed with [docker] and [proxmox] respectively depending on where they need to be run.

It makes no difference which Proxmox node you pick for the initial set up, but being able to directly transfer files (e.g. via scp) between it and the docker host will make it easier.

  1. [docker] Pull the docker corosync-qnetd container (or build it from this repo)

    docker pull modelrockettier/corosync-qnetd
    
  2. [docker] Create and start the docker corosync-qnetd container:

    docker run -d --name=qnetd --cap-drop=ALL -p 5403:5403 \
       -v ${QNETD_DATA}:/etc/corosync modelrockettier/corosync-qnetd
    
  3. [docker] Copy the QNetd CA certificate to the first Proxmox node:

    scp ${QNETD_DATA}/qnetd/nssdb/qnetd-cacert.crt \
         ${PROXMOX_NODE}:/etc/pve/corosync/qdevice/net/nssdb/
    
    • NOTE: Since the Proxmox cluster already synchronizes everything in the /etc/pve directory, it's easiest to just copy the CA certificate there on 1 node, and it'll automatically propogate to all other nodes. This way you won't need to copy it over to the other nodes individually.
  4. [proxmox] Install the corosync-qdevice package on the first Proxmox node:

    apt-get install corosync-qdevice
    
  5. [proxmox] Start and enable the corosync-qdevice service on the first Proxmox node:

    systemctl start corosync-qdevice
    systemctl enable corosync-qdevice
    
    • NOTE: if enable fails, try deleting /etc/init.d/corosync-qdevice and try again. See <[***]>
  6. [proxmox] Initialize the corosync-qdevice certificate database on the first Proxmox node:

    corosync-qdevice-net-certutil -i \
       -c /etc/pve/corosync/qdevice/net/nssdb/qnetd-cacert.crt
    
  7. [proxmox] Generate a certificate signing request on the first Proxmox node:

    corosync-qdevice-net-certutil -r -n ${CLUSTER_NAME}
    
  8. [docker] Copy the certificate signing request to the corosync config directory:

    scp ${PROXMOX_NODE}:/etc/corosync/qdevice/net/nssdb/qdevice-net-node.crq \
       ${QNETD_DATA}/qnetd/nssdb/
    
  9. [docker] Sign the certificate from the corosync-qnetd container:

    docker exec qnetd \
       corosync-qnetd-certutil -s -n ${CLUSTER_NAME} \
          -c /etc/corosync/qnetd/nssdb/qdevice-net-node.crq
    
    • Note the path to the .crq is from inside the container.
  10. [docker] Copy the newly generated certificate back to the first Proxmox node:

    scp ${QNETD_DATA}/qnetd/nssdb/cluster-${CLUSTER_NAME}.crt \
       ${PROXMOX_NODE}:/etc/pve/corosync/qdevice/net/nssdb/
    
  11. [proxmox] Import the certificate on the first Proxmox node:

    corosync-qdevice-net-certutil -M -c cluster-${CLUSTER_NAME}.crt
    
  12. [proxmox] Copy the output qdevice-net-node.p12 to all other Proxmox nodes:

    cp -v /etc/corosync/qdevice/net/nssdb/qdevice-net-node.p12 \
       /etc/pve/corosync/qdevice/net/nssdb/
    
    • NOTE: We're again using the /etc/pve synchronization discussed in step 3.
  13. [proxmox] Set up all other Proxmox nodes

    1. Repeat steps 4-6 above

      1. Install the corosync-qdevice package

      2. Start and enable the corosync-qdevice service

      3. Initialize the corosync-qdevice certificate database

        corosync-qdevice-net-certutil -i \
           -c /etc/pve/corosync/qdevice/net/nssdb/qnetd-cacert.crt
        
    2. Import the corosync cluster certificate and key:

      corosync-qdevice-net-certutil -m \
         -c /etc/pve/corosync/qdevice/net/nssdb/qdevice-net-node.p12
      
  14. [proxmox] Add qdevice config to /etc/pve/corosync.conf on the first Proxmox node:

    Edit /etc/pve/corosync.conf:

    • Replace:
      quorum {
          provider: corosync_votequorum
      }
      
    • With the following (and change ${DOCKER_HOST} to the hostname or IP of your docker host):
      quorum {
          provider: corosync_votequorum
          device {
              model: net
              votes: 1
              net {
                  tls: on
                  host: ${DOCKER_HOST}
                  algorithm: ffsplit
              }
          }
      }
      

    See <[***]> for more info.

  15. [proxmox] Restart the corosync-qdevice service on all Proxmox nodes:

systemctl restart corosync-qdevice
  1. [docker] Ensure corosync-qnetd is working properly

The number of connected clients should be equal to the number of proxmox nodes online.

Quick Setup (untested/unsupported)

This should work and be a bit quicker and easier than the above quick start guide, but it hasn't been tested and requires your proxmox nodes to be able to SSH into your docker host.

Prerequisites

Your docker host must have an SSH server installed and the Proxmox node used in step 5 must be able to SSH into your docker server.

You will also need to set a few environment variables (or manually replace them with the appropriate values in the commands below):

  • CLUSTER_NAME: The name of your Proxmox cluster (must match the cluster_name key in /etc/corosync/corosync.conf on your Proxmox nodes.

    E.g.

    CLUSTER_NAME=pm-cluster-1
    
  • DOCKER_HOST: The hostname or IP address of your docker host

    E.g.

    DOCKER_HOST=docker1
    
  • PROXMOX_NODES: The hostnames or IP addresses of your proxmox nodes

    E.g.

    PROXMOX_NODES=( proxmox1 proxmox2 )
    
Instructions
  1. On all Proxmox nodes, install the corosync-qdevice package:

    apt-get install corosync-qdevice
    
  2. On all Proxmox nodes, start and enable the corosync-qdevice service:

    systemctl start corosync-qdevice
    systemctl enable corosync-qdevice
    
  3. On the docker host, create and start the docker corosync-qnetd container:

    docker run -d --name=qnetd --cap-drop=ALL -p 5403:5403 \
       -v /etc/corosync:/etc/corosync modelrockettier/corosync-qnetd
    
    • NOTE: The corosync-qnetd data must be stored in /etc/corosync on the docker host.
  4. On the docker host, copy the QNetd tools into the $PATH:

    sudo docker cp qnetd:/usr/bin/corosync-qnetd-tool     /usr/local/bin/
    sudo docker cp qnetd:/usr/bin/corosync-qnetd-certutil /usr/local/bin/
    
  5. From a Proxmox node, run the Proxmox cluster qdevice setup

    pvecm qdevice setup ${DOCKER_HOST}
    
    • The corosync-qdevice-net-certutil quick setup may also work (again, this is untested).
      corosync-qdevice-net-certutil -Q -n ${CLUSTER_NAME}
             ${DOCKER_HOST} ${PROXMOX_NODES[@]}
      
  6. On the docker host, Ensure corosync-qnetd is working properly

    The number of connected clients should be equal to the number of proxmox nodes online.

Check on a running Corosync QNet Daemon

docker exec qnetd corosync-qnetd-tool -s
Example output
QNetd address:                  *:5403
TLS:                            Supported (client certificate required)
Connected clients:              2
Connected clusters:             1
查看更多 corosync-qnetd 相关镜像 →
0xygen1337/pve-corosync-qdevice-voter logo
0xygen1337/pve-corosync-qdevice-voter
0xygen1337
Simple docker container to deploy a qdevice voter for Proxmox PVE to act as third fake node
10K+ pulls
上次更新:1 年前
ocl80/proxmoxqnetd logo
ocl80/proxmoxqnetd
ocl80
暂无描述
10K+ pulls
上次更新:1 年前
safhdev/corosyncdevice logo
safhdev/corosyncdevice
safhdev
一个可创建功能性corosync-d服务的Docker镜像,适用于Proxmox等corosync集群环境,基于Debian或Ubuntu构建,支持多平台并提供服务监控功能。
10K+ pulls
上次更新:3 个月前
ibmcom/corosync-ppc64le logo
ibmcom/corosync-ppc64le
ibmcom
Corosync集群引擎,用于提供高可用性集群通信服务。
245 pulls
上次更新:7 年前

轩辕镜像配置手册

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

登录仓库拉取

通过 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访问体验非常流畅,大镜像也能快速完成下载。"

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