<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Databricks Container Services now available for Standard Compute - custom Docker images in shared co in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/databricks-container-services-now-available-for-standard-compute/m-p/157528#M1198</link>
    <description>&lt;P&gt;Databricks has a new/updated feature in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Beta&lt;/STRONG&gt;:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Databricks Container Services for standard compute&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Docs:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://docs.databricks.com/aws/en/compute/custom-containers-standard?utm_source=chatgpt.com" target="_blank" rel="noopener nofollow ugc"&gt;https://docs.databricks.com/aws/en/compute/custom-containers-standard&lt;/A&gt;&lt;/P&gt;&lt;P&gt;With this feature, you can specify a Docker image when creating&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;standard compute&lt;/STRONG&gt;, which means custom workload environments can now be used in shared compute scenarios too.&lt;/P&gt;&lt;P&gt;A few things worth to mention:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Requires Standard access mode + DBR 18.3+&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks provides a base image - The recommended approach is to extend:FROM databricksruntime/environment:v5-standard&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Python dependencies should go into&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/databricks/python3&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Example:RUN /databricks/python3/bin/python -m pip install simplejson&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;This seems important because notebooks, Python wheel jobs, and Python script jobs read from this environment.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Some Dockerfile instructions are ignored - instructions like&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;USER,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;CMD,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ENTRYPOINT,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;EXPOSE,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;HEALTHCHECK,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;SHELL, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;STOPSIGNAL&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;are ignored because of how workloads are launched.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Init scripts no longer modify the workload Python environment - this is a big migration point. If your old setup used init scripts to install Python packages, those dependencies now need to move into the Docker image.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Not everything is supported yet - current limitations include no compute-scoped libraries, no private package repositories, and no Databricks Runtime for Machine Learning support.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;ECR support uses instance profiles - for Amazon ECR images, authentication is handled through an instance profile with permission to pull the image.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This seems like a pretty important step toward reproducible Databricks environments, especially for teams that want parity between local/dev/prod environments without relying heavily on init scripts or ad-hoc cluster libraries.&lt;/P&gt;</description>
    <pubDate>Sat, 23 May 2026 07:25:13 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2026-05-23T07:25:13Z</dc:date>
    <item>
      <title>Databricks Container Services now available for Standard Compute - custom Docker images in shared co</title>
      <link>https://community.databricks.com/t5/community-articles/databricks-container-services-now-available-for-standard-compute/m-p/157528#M1198</link>
      <description>&lt;P&gt;Databricks has a new/updated feature in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Beta&lt;/STRONG&gt;:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Databricks Container Services for standard compute&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Docs:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://docs.databricks.com/aws/en/compute/custom-containers-standard?utm_source=chatgpt.com" target="_blank" rel="noopener nofollow ugc"&gt;https://docs.databricks.com/aws/en/compute/custom-containers-standard&lt;/A&gt;&lt;/P&gt;&lt;P&gt;With this feature, you can specify a Docker image when creating&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;standard compute&lt;/STRONG&gt;, which means custom workload environments can now be used in shared compute scenarios too.&lt;/P&gt;&lt;P&gt;A few things worth to mention:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Requires Standard access mode + DBR 18.3+&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks provides a base image - The recommended approach is to extend:FROM databricksruntime/environment:v5-standard&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Python dependencies should go into&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;/databricks/python3&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Example:RUN /databricks/python3/bin/python -m pip install simplejson&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;This seems important because notebooks, Python wheel jobs, and Python script jobs read from this environment.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Some Dockerfile instructions are ignored - instructions like&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;USER,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;CMD,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;ENTRYPOINT,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;EXPOSE,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;HEALTHCHECK,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;SHELL, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;STOPSIGNAL&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;are ignored because of how workloads are launched.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Init scripts no longer modify the workload Python environment - this is a big migration point. If your old setup used init scripts to install Python packages, those dependencies now need to move into the Docker image.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Not everything is supported yet - current limitations include no compute-scoped libraries, no private package repositories, and no Databricks Runtime for Machine Learning support.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;ECR support uses instance profiles - for Amazon ECR images, authentication is handled through an instance profile with permission to pull the image.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This seems like a pretty important step toward reproducible Databricks environments, especially for teams that want parity between local/dev/prod environments without relying heavily on init scripts or ad-hoc cluster libraries.&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2026 07:25:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/databricks-container-services-now-available-for-standard-compute/m-p/157528#M1198</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2026-05-23T07:25:13Z</dc:date>
    </item>
  </channel>
</rss>

