cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect to the cluster

Prashiratnam123
New Contributor II

Container launch failure:

An unexpected error was encountered while launching containers on worker instances for the cluster. Please retry and contact Databricks if the problem persists.

Instance ID: i-02aadc9a7c3532af0

Internal error message: Failed to launch spark container on instance i-02aadc9a7c3532af0. Exception: Unexpected internal error, please contact Databricks support.
 
Please help me to resole this issue
4 REPLIES 4

Alberto_Umana
Databricks Employee
Databricks Employee

Hello @Prashiratnam123, Is this error observed consistently?

Which region is your workspace on and when did this happen?

Yes, it's happening consistently, forgot the region.

Please help me to resolve( how to get the region details)

Isi
Contributor

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. 🚀

Prashiratnam123
New Contributor II

hi

 

I'm using community addition.

Regards,

Sundaram