https://community.databricks.com/t5/data-engineering/using-your-own-docker-container-to-launch-databricks-cluster/m-p/11614#M6562 <P>+1</P> Wed, 01 Feb 2023 18:16:54 GMT FRG96 2023-02-01T18:16:54Z https://community.databricks.com/t5/data-engineering/using-your-own-docker-container-to-launch-databricks-cluster/m-p/11613#M6561 <P>When using your own docker container while creating a databricks cluster, what is the mapping between the number of containers launched and the nodes launched?</P><P>Is it 1:1 mapping? or is it similar to other orchestration framework like Kubernetes?</P><P>Or is it node based? like driver node has a different mapping compared to worker nodes?</P><P>In documentation it says, internally databricks container service is used to launch docker container, but we do not get a clear picture as to how the orchestration is done.</P><P>I need to understand this underlying orchestration, as I have a use case where I need to run a service within a container only on the driver node and not on the worker nodes &amp; need to endure that only one such container is running on the driver node.</P> Tue, 17 Jan 2023 10:22:58 GMT https://community.databricks.com/t5/data-engineering/using-your-own-docker-container-to-launch-databricks-cluster/m-p/11613#M6561 229031 2023-01-17T10:22:58Z https://community.databricks.com/t5/data-engineering/using-your-own-docker-container-to-launch-databricks-cluster/m-p/11614#M6562 <P>+1</P> Wed, 01 Feb 2023 18:16:54 GMT https://community.databricks.com/t5/data-engineering/using-your-own-docker-container-to-launch-databricks-cluster/m-p/11614#M6562 FRG96 2023-02-01T18:16:54Z