Docker seekdb deployment with init SQL fails to execute initialization scripts

Environment

• Version: OceanBase seekdb 1.2.0.0
• Source Revision: 100000222026032420-bde98aeaa8740119c4a2aa420138c838312e6708
• Deployment Method: Docker

Description

When deploying the seekdb Docker container with initialization SQL scripts, the scripts are not successfully executed. The container starts, but the specified SQL for initial setup does not run.

Steps to Reproduce

1. Deploy the seekdb Docker container with a configuration that includes initialization SQL scripts (e.g., via environment variables or mounted volumes).
2. Start the container.
3. Observe that the container process (seekdb) starts, as indicated by the version output.
4. Check the database state; the expected tables, data, or users defined in the init SQL are not present.

Impact

The database is not in the expected initial state after deployment, requiring manual intervention to run setup scripts. This breaks automated deployment and provisioning workflows that rely on a fully initialized instance.

Proposed Solution

Investigate the Docker entrypoint or startup sequence to ensure initialization SQL hooks are correctly triggered after the seekdb process is ready to accept connections. The fix should ensure compatibility with common methods for providing init SQL (e.g., /docker-entrypoint-initdb.d/ pattern or specific environment variables).

Inspect the Docker entrypoint and startup sequence, using the reported environment-variable and mounted-volume initialization methods, including /docker-entrypoint-initdb.d/. Reproduce the deployment and verify that init SQL runs after seekdb accepts connections; done means the expected tables, data, or users are present without manual intervention.