DolphinDB ddb_cluster_quick Startup Failure

[R0ck-crypto]

Description

Containers fail to start when using image dolphindb/dolphindb:v3.00.2.1 in ddb_cluster_quick example setup.

Environment

• ddb_cluster_quick example configuration
• Docker Compose
• DolphinDB Image: dolphindb/dolphindb:v3.00.2.1
• Platform: macOS

Steps to Reproduce

1. Navigate to ddb_cluster_quick directory
2. Change image version to dolphindb/dolphindb:v3.00.2.1
3. Run docker compose up -d
4. Check status with docker compose ps

Current Behavior

Both containers are continuously restarting with segmentation fault:

NAME             IMAGE                           COMMAND                  SERVICE          CREATED          STATUS                          PORTS
ddb_agent1       dolphindb/dolphindb:v3.00.2.1   "sh -c 'cd /data/ddb…"   ddb_agent1       15 seconds ago   Restarting (139) 1 second ago   
ddb_controller   dolphindb/dolphindb:v3.00.2.1   "sh -c 'cd /data/ddb…"   ddb_controller   16 seconds ago   Restarting (139) 1 second ago   

[peeyee]

You can refer to log for more details，especially the ERROR messages。Typically the logfile resides on （HOST_CON_LOG=${HOST_CON}/log），see .env （use ls -a) configuration file。

[R0ck-crypto]

Tried running the containers and got immediate segmentation faults without any log generation:

[+] Running 3/0
✔ Network dev_ddb           Created                                          0.0s 
✔ Container ddb_controller  Created                                          0.0s 
✔ Container ddb_agent1      Created                                          0.0s 
Attaching to ddb_agent1, ddb_controller
ddb_controller exited with code 139
ddb_agent1 exited with code 139

Both containers fail immediately with exit code 139 (segmentation fault) before any logs are generated. The containers aren't running long enough to create log files for investigation. This appears to be a fundamental startup issue.

Environment:

macOS
docker compose
Image: dolphindb/dolphindb:v3.00.2.1