cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Standard_NC8as_T4_v3" and "Standard_NC4as_T4_v3" instances

amoghjain
New Contributor II

I am running into an issue where "Standard_NC8as_T4_v3" and "Standard_NC4as_T4_v3" instances are behaving differently for a 30gb custom docker image, and I am a bit stumped.

when using NC4 instances, I get a timeout, with the exact message shown below

Message

Compute terminated. Reason: Docker image pull failure

Help

Cannot launch the cluster because pulling the docker image failed. Please double check connectivity from workers to the container registry, as well as the credentials used to pull the image.

Instance ID: ------hidden for privacy-----

Internal error message: Container setup failed due to a docker image pull failure: Exception when downloading docker container image: Timed out with exception after 23927 attempts


Now, I am  bit surprised and trying to find out why do NC4 instances have timeout issues, where as NC8 do not. Any help or pointers would be appreciated!
 
Have a nice day!!
 
Thanks
 

 

0 REPLIES 0

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group