UBA Docker Deployment Guide

This document is aimed at operations engineers, covering GoWind UBA's two Docker deployment modes, the full-stack compose service inventory, the shared Dockerfile, and the build process.

Read System Architecture and the Configuration Reference first. Default passwords/secrets must be rotated; see the security checklist in the Configuration Reference.

1. Two Deployment Modes

The scripts automatically detect docker compose (v2 plugin) or fall back to docker-compose, and pre-create the dependency data directories (postgres/redis/etcd/minio/jaeger).

2. Quick Start

Linux / macOS

cd backend
chmod +x scripts/**/*.sh

# Start middleware dependencies only (recommended for development)
./scripts/docker/libs_only.sh

# One-click full deployment (middleware + three backend services)
./scripts/docker/full_deploy.sh

Windows (PowerShell as Administrator)

cd backend
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser   # first-time allowance

.\scripts\docker\libs_only.ps1
# or
.\scripts\docker\full_deploy.ps1

Equivalent Make Commands

cd backend
make docker-libs   # OS-aware: automatically calls the platform's libs_only script
make docker-up     # OS-aware: automatically calls full_deploy
make docker-down   # docker compose down

3. Full-Stack Service Inventory (docker-compose.yaml)

All services join the app-tier bridge network, with timezone TZ=Asia/Shanghai.

Middleware

The compose file also has commented-out blocks for consul, mysql/mariadb, and clickhouse; uncomment as needed.

Application Services

The three services share the same Dockerfile, selecting which binary to compile via the build argument SERVICE_NAME:

The port mappings match the services' server.yaml listening ports (admin 5600/5601, collector 5700); access them from the host directly via the corresponding ports. See Configuration Reference · Port Reference for details.

libs Mode

docker-compose.libs.yaml is exactly the same as the full version in its middleware section, but excludes the three application services admin/collector/core — this is the libs_only mode, where the backend is started locally with go run for debugging.

4. Building the Application Images

cd backend

# Method 1: recursively build an image for each service
make docker

# Method 2: build in a single service directory
cd app/admin/service
make docker   # docker build -t $PROJECT_NAME/$APP_NAME --build-arg SERVICE_NAME=admin ...

The Dockerfile (backend/Dockerfile) controls the artifacts via --build-arg SERVICE_NAME={admin|collector|core} and --build-arg APP_VERSION=..., producing minimal images through multi-stage builds.

5. Network & Dependency Details

• Application network: all three services are on app-tier and communicate via service names (admin calls core's gRPC, discovered via etcd; core's gRPC uses a dynamic port, not fixed at 5600).
• Doris static IPs: FE/BE use 172.20.80.x static addresses (required by Doris cluster configuration); do not change the network segment arbitrarily.
• Kafka advertised listener: inside compose, Kafka advertises kafka:9092 to containers, while the collector's data.yaml defaults to 127.0.0.1:9092. For containerized deployment, change the collector's kafka address to kafka:9092.
• Postgres database name: compose has unified POSTGRES_DB=gw_uba, consistent with dbname=gw_uba in the services' data.yaml, so no extra alignment is needed.

6. Health Checks & Troubleshooting

Use the Jaeger UI (http://localhost:16686) to inspect cross-service calls for distributed tracing.

7. Related Documentation

• System Architecture
• Configuration Reference (security checklist)
• PM2 Deployment
• Superset Deployment
• Appendix · Port Reference