apecloud/apecloud-postgres Docker 镜像 - 轩辕镜像
apecloud/apecloud-postgresapecloud
0 次下载
What is apecloud postgres?
ApeCloud postgres offering is committed to providing a robust and highly available database solution. This is achieved by integrating "postgres with consensus hook" and implementing the raft consensus algorithm through a "consensus extension." The comprehensive architecture is meticulously designed to minimize data loss, boasting an impressive Recovery Point Objective (RPO) of 0, which essentially eliminates acceptable data loss. Moreover, the system is geared towards ensuring rapid recovery in the face of failures, exemplified by a low Recovery Time Objective (RTO).
How to use this image?
- create container network
docker network create --driver bridge \ --gateway=192.168.0.1 --subnet 192.168.0.0/24 \ my_pg_network
- create a leader node
docker run -d \ --name test-apepg1 \ --network my_pg_network \ --ip 192.168.0.2 \ -p 54322:5432 \ -e POSTGRES_HOST_AUTH_METHOD=md5 \ -e POSTGRES_PASSWORD=password \ -e CONSENSUS_MODE=leader \ -e CONSENSUS_POSTGRESQL_HOST=192.168.0.2 \ apecloud/apecloud-postgres:14.10-0.7.0
- check leader node role
PGPASSWORD=password psql -Upostgres -h127.0.0.1 -p 54322 \ -c "select role from consensus_member_status"
- create the first follower node
docker run -d \ --name test-apepg2 \ --network my_pg_network \ --ip 192.168.0.3 \ -p 54323:5432 \ -e POSTGRES_HOST_AUTH_METHOD=md5 \ -e POSTGRES_PASSWORD=password \ -e CONSENSUS_MODE=follower \ -e CONSENSUS_POSTGRESQL_HOST=192.168.0.3 \ -e CONSENSUS_CLUSTER_LEADER_HOST=192.168.0.2 \ -e CONSENSUS_CLUSTER_LEADER_PORT=5432 \ apecloud/apecloud-postgres:14.10-0.7.0
- create the second follower node
docker run -d \ --name test-apepg3 \ --network my_pg_network \ --ip 192.168.0.4 \ -p 54324:5432 \ -e POSTGRES_HOST_AUTH_METHOD=md5 \ -e POSTGRES_PASSWORD=password \ -e CONSENSUS_MODE=follower \ -e CONSENSUS_POSTGRESQL_HOST=192.168.0.4 \ -e CONSENSUS_CLUSTER_LEADER_HOST=192.168.0.2 \ -e CONSENSUS_CLUSTER_LEADER_PORT=5432 \ apecloud/apecloud-postgres:14.10-0.7.0
- check postgres consensus cluster status
PGPASSWORD=password psql -Upostgres -h127.0.0.1 -p 54322 \ -c "select * from consensus_cluster_status"
server_id | ip_port | match_index | next_index | role | has_voted | force_sync | election_weight | learner_source | pipelining -----------+-------------------+-------------+------------+----------+-----------+------------+-----------------+----------------+------------ 1 | 192.168.0.2:*** | 23 | 0 | Leader | t | f | 5 | 0 | f 2 | 192.168.0.3:*** | 23 | 24 | Follower | f | f | 5 | 0 | t 3 | 192.168.0.4:*** | 23 | 24 | Follower | f | f | 5 | 0 | t (3 rows)
- connect a client to the Leader node
$ PGPASSWORD=password psql -Upostgres -h127.0.0.1 -p 5432 psql (14.10 (with consensus 0.7.0 PGTAG=CONSENSUS_HOOK_2_1_0_PG_14_10)) Type "help" for help. postgres=# select version(); version ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- PostgreSQL 14.10 (with consensus 0.7.0 PGTAG=CONSENSUS_HOOK_2_1_0_PG_14_10) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
Docker Environment Variables
CONSENSUS_MODE
The current instance is enabled with the consensus feature by setting the CONSENSUS_MODE environment variable, and the instance is started with the specified role.
-e CONSENSUS_MODE={leader | follower}
If it is a leader: Initialize a new instance, add consensus configuration parameters to the postgresql.conf file, and then start the instance. It's important to note that if a custom postgresql.conf configuration file is used through the POSTGRESQL_MOUNTED_CONF_DIR environment variable when the container starts, the postgresql.conf won't be reconfigured.The following parameters must be set in the postgresql.conf configuration file:
shared_preload_libraries = 'consensus' consensus.consensus_enabled = true
If it is a follower: Backup data from the leader node based on the specified CONSENSUS_CLUSTER_LEADER_HOST and CONSENSUS_CLUSTER_LEADER_PORT parameters, then join the cluster in the follower role.
CONSENSUS_POSTGRESQL_HOST
The IP address of the current instance serving as a consensus cluster node is used with the default PORT of 5432. This 'IP:PORT' combination is utilized for the interaction of consensus information among various nodes in the consensus cluster.
-e CONSENSUS_POSTGRESQL_HOST=192.168.0.3
CONSENSUS_CLUSTER_LEADER_HOST
The IP for the existing Consensus cluster's Leader role node.
-e CONSENSUS_CLUSTER_LEADER_HOST=192.168.0.2
CONSENSUS_CLUSTER_LEADER_PORT
The PORT for the existing Consensus cluster's Leader role node.
-e CONSENSUS_CLUSTER_LEADER_PORT=5432
POSTGRESQL_REPLICATION_USER
The replication user created on the leader on first run. 'replicator' defaults.
-e POSTGRESQL_REPLICATION_USER=repl
POSTGRESQL_REPLICATION_PASSWORD
The replication users password. 'replicator' defaults.
-e POSTGRESQL_REPLICATION_PASSWORD=password
POSTGRESQL_MOUNTED_CONF_DIR
Specify the directory for externally mounted configuration files. When Docker startup, the files located in the mounted directory, under POSTGRESQL_MOUNTED_CONF_DIR, will be copied to the PGDATA directory, thereby overwriting the postgresql.conf and pg_hba.conf files.
-e POSTGRESQL_MOUNTED_CONF_DIR=/conf \ -v /u01/conf:/conf
Docker Secrets
As an alternative to passing sensitive information via environment variables, _FILE may be appended to some of the previously listed environment variables, causing the initialization script to load the values for those variables from files present in the container. In particular, this can be used to load passwords from Docker secrets stored in /run/secrets/<secret_name> files. Currently, this is only supported for POSTGRESQL_REPLICATION_USER, POSTGRESQL_REPLICATION_PASSWORD, POSTGRES_INITDB_ARGS, POSTGRES_PASSWORD, POSTGRES_USER, and POSTGRES_DB.For example:
echo "apecloud" > /u01/secret/postgres_user.txt echo "mypassword" > /u01/secret/postgres_password.txt echo "repl" > /u01/secret/postgres_replication_user.txt echo "repl_password" > /u01/secret/postgres_replication_password.txt docker run -d \ --name test-apepg \ -e POSTGRES_USER_FILE=/run/secrets/postgres_user.txt \ -e POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password.txt \ -e POSTGRESQL_REPLICATION_USER_FILE=/run/secrets/postgres_replication_user.txt \ -e POSTGRESQL_REPLICATION_PASSWORD_FILE=/run/secrets/postgres_replication_password.txt \ -v /u01/secret:/run/secrets \ apecloud/apecloud-postgres:14.10-0.7.0
.backup_restore
If starting as a follower role by mounting the data directory to /var/lib/postgresql/data using the -v parameter, it is necessary to create a .backup_restore file in the data directory. If this file is not created, the new consensus cluster will be started directly as a Leader role.
PGPASSWORD=replicator pg_basebackup -h 127.0.0.1 -p 54322 -U replicator -w \ -D $PWD/pgconsensus_volume2 -X stream \ -P -v cd $PWD/pgconsensus_volume2 echo "" >> .backup_restore -v $PWD/pgconsensus_volume2:/var/lib/postgresql/data
Example
docker run -d \ --name test-apepg \ --network my_pg_network \ --ip 192.168.0.2 \ -p 54322:5432 \ -e CONSENSUS_MODE=leader \ -e CONSENSUS_POSTGRESQL_HOST=192.168.0.2 \ -e CONSENSUS_CLUSTER_LEADER_HOST=192.168.0.2 \ -e POSTGRESQL_MOUNTED_CONF_DIR=/conf \ -v /u01/conf:/conf \ -e POSTGRES_HOST_AUTH_METHOD=md5 \ -e POSTGRES_DB=apecloud \ -e POSTGRES_USER=apecloud \ -e POSTGRES_PASSWORD_FILE=/run/secrets/postgres_password.txt \ -e POSTGRESQL_REPLICATION_USER=repl \ -e POSTGRESQL_REPLICATION_PASSWORD_FILE=/run/secrets/postgres_replication_password.txt \ -v /u01/secret:/run/secrets \ -e POSTGRES_INITDB_ARGS="--data-checksums" \ -e POSTGRES_INITDB_WALDIR="/waldir" \ -v /u01/initdb-scripts:/docker-entrypoint-initdb.d \ apecloud/apecloud-postgres:14.10-0.7.0
postgres
Docker 官方镜像
PostgreSQL作为一款功能强大的对象关系型数据库系统，凭借其先进的架构设计与完善的技术机制，不仅能高效融合关系型数据的结构化管理与对象型数据的灵活扩展，更通过严格的ACID事务支持、多版本并发控制及全面的数据校验机制，为各类应用场景提供卓越的系统可靠性与极致的数据完整性保障，是全球广泛应用的开源数据库优选方案。
147611B+ pulls
上次更新：12 天前
cimg/postgres
cimg
CircleCI便捷镜像，集成PostgreSQL数据库，用于CI/CD流程中快速部署和运行PostgreSQL相关的测试及开发任务，简化配置。
7500M+ pulls
上次更新：7 天前
bitnami/postgresql
bitnami
Bitnami PostgreSQL安全镜像是一款专为PostgreSQL数据库设计的预配置、安全强化型容器镜像，集成自动更新的安全补丁、最小化攻击面架构、合规性验证工具及行业最佳安全实践，旨在简化数据库部署流程，同时保障数据存储与访问的安全性、稳定性及可靠性，适用于企业级应用场景下高效、安全的数据库环境搭建。
3711B+ pulls
上次更新：8 天前
docker/dtr-postgres
Docker 官方工具与组件镜像
暂无描述
1M+ pulls
上次更新：5 年前
airbyte/source-postgres
airbyte
暂无描述
5M+ pulls
上次更新：4 天前
bitnami/postgres-exporter
bitnami
Bitnami提供的安全镜像，用于部署postgres-exporter，可将PostgreSQL数据库指标导出至监控系统，具备安全加固特性。
1950M+ pulls
上次更新：12 天前
轩辕镜像配置手册
探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式
登录仓库拉取
通过 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访问体验非常流畅，大镜像也能快速完成下载。"
咨询镜像拉取问题请 提交工单，官方技术交流群：1072982923
轩辕镜像面向开发者与科研用户，提供开源镜像的搜索和访问支持。所有镜像均来源于原始仓库，本站不存储、不修改、不传播任何镜像内容。