ARM64 Docker image fails because ibm_db binding is missing

[st3k0]

Describe the bug
The ARM64 variant of rocketadmin/rocketadmin:latest starts PostgreSQL migrations successfully but then crashes because the bundled ibm_db module cannot locate an ARM64 native binding.

To Reproduce
Steps to reproduce the behavior:

1. Deploy rocketadmin/rocketadmin:latest on an ARM64 VPS.
2. Deploy using Docker/Dokploy without forcing linux/amd64.
3. Connect Rocketadmin to a separate PostgreSQL service over the shared Docker network.
4. Start the Rocketadmin container.
5. Check the container logs.

Expected behavior
The ARM64 Docker image should start successfully and serve the Rocketadmin UI.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Linux VPS
• Host architecture: ARM64 / aarch64
• Deployment platform: Dokploy
• Docker image: rocketadmin/rocketadmin:latest
• Image platform: linux/arm64
• Node.js version inside container: v24.19.0
• Database: PostgreSQL, separate Dokploy service
• Browser: Not applicable

Additional context
The Docker Hub latest tag provides both linux/amd64 and linux/arm64 images.
Forcing the AMD64 image on the ARM64 VPS results in:

exec /app/backend/entrypoint.sh: exec format error

Using the native ARM64 image avoids the architecture error, but then fails because the ibm_db native binding is missing.

The PostgreSQL connection is working; migrations complete successfully before the ibm_db error occurs.