Unable to connect to the cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2025 06:27 PM
Container launch failure:
Instance ID: i-02aadc9a7c3532af0
Internal error message: Failed to launch spark container on instance i-02aadc9a7c3532af0. Exception: Unexpected internal error, please contact Databricks support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2025 10:20 AM
Hello @Prashiratnam123, Is this error observed consistently?
Which region is your workspace on and when did this happen?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Yes, it's happening consistently, forgot the region.
Please help me to resolve( how to get the region details)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hey @Prashiratnam123
Could you provide more details on how you are trying to install the container?
1. Are you using a custom Docker image or a base Databricks container?
2.Are you mixing architectures (Graviton ARM vs. AMD64)? Some instances in AWS (like m6g, c7g) run on ARM architecture, which might not be compatible with AMD64-based Docker images.
3.Are there any errors in the cluster event logs? You can check the event logs in the Databricks UI under Clusters > Event Log to see if there are more details on why the container failed to launch.
If possible, please share the following details:
•The Docker image name and tag
•The Databricks runtime version
•The instance type you are using (m5, m6g, etc.)
This will help diagnose the issue faster. 🚀
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
hi
I'm using community addition.
Regards,
Sundaram

