oceanbase/oceanbase-ceThe oceanbase-ce Docker image, available on dockerhub, quay.io and ghcr.io, is designed for users to quickly set up an OceanBase environment for testing purposes.
Before deploying oceanbase-ce, ensure that the following requirements are met:
To start an OceanBase instance, use one of the following docker run commands:
bash# Deploy a mini mode instance docker run -p 2881:2881 --name oceanbase-ce -d oceanbase/oceanbase-ce # Deploy an instance to utilize the full resource of the container docker run -p 2881:2881 --name oceanbase-ce -e MODE=normal -d oceanbase/oceanbase-ce # Deploy an instance using fastboot mode docker run -p 2881:2881 --name oceanbase-ce -e MODE=slim -d oceanbase/oceanbase-ce # Execute init SQL scripts after bootstrap, do not change root user's password in SQL scripts. # If you'd like to change root user's password, use variable OB_TENANT_PASSWORD. docker run -p 2881:2881 --name oceanbase-ce -v {init_sql_folder_path}:/root/boot/init.d -d oceanbase/oceanbase-ce
The bootstrap procedure may take up to five minutes. Verify the bootstrap completion by running:
docker logs oceanbase-ce | tail -1
Expected output:
boot success!
Note:
For local connections using obclient or mysql client:
mysql -h127.0.0.1 -P2881 -uroot # Connect with the root account of sys tenant mysql -h127.0.0.1 -P2881 -uroot@test # Connect with the root account of a general tenant
Below is a table of supported environment variables for the image:
| Variable name | Default value | Description |
|---|---|---|
| MODE | {mini, slim, normal} | mini indicates that the container will use the least amount of resource normal indicates that the container will use as much as possible of the container resource slim indicates that the container will only start observer using fastboot mode, the tenant is named as test, tenant and resource configurations will not take effect. |
| EXIT_WHILE_ERROR | true | Whether quit the container when failed to start observer. if you set EXIT_WHILE_ERROR=false, the container will not exit and you can use log into the container for debugging. |
| OB_CLUSTER_NAME | obcluster | The oceanbase cluster name |
| OB_TENANT_NAME | test | The oceanbase mysql tenant name |
| OB_MEMORY_LIMIT | 6G | The oceanbase cluster memory_limit configuration |
| OB_DATAFILE_SIZE | 5G | The oceanbase cluster datafile_size configuration |
| OB_LOG_DISK_SIZE | 5G | The oceanbase cluster log_disk_size configuration |
| OB_SYS_PASSWORD | The oceanbase root user password of sys tenant | |
| OB_TENANT_PASSWORD | The oceanbase root user password of mysql tenant | |
| OB_SYSTEM_MEMORY | 1G | The oceanbase cluster system_memory configuration |
| OB_TENANT_MINI_CPU | The oceanbase tenant mini_cpu configuration | |
| OB_TENANT_MEMORY_SIZE | The oceanbase tenant memory_size configuration | |
| OB_TENANT_LOG_DISK_SIZE | The oceanbase tenant log_disk_size configuration |
The oceanbase-ce image includes the sysbench tool for benchmarking. Use the following command to run a sysbench test:
docker exec -it oceanbase-ce obd test sysbench obcluster
By default, oceanbase-ce deploys OceanBase under /root/ob and saves its configurations under /root/.obd/cluster. Use the following command to persist data on the host:
mkdir -p ob mkdir -p obd/cluster docker run -d -p 2881:2881 -v $PWD/ob:/root/ob -v $PWD/obd/cluster:/root/.obd/cluster --name oceanbase oceanbase/oceanbase-ce
The enable_rich_error_msg parameter is enabled by default during Docker startup. If an error occurs, you can obtain detailed error information using the trace command.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
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 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务