<?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 Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32420#M23620</link>
    <description>&lt;P&gt;Long time has passed and I have a solution to get things working. I do have the logs, but haven't really paid much attention to this lately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To me, this is  a regression issue in Azure Databricks. When a new version of a node is released, it should be tested with containers too. If old node versions are not, maybe I should be informed about it.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Mar 2022 10:05:39 GMT</pubDate>
    <dc:creator>HQJaTu</dc:creator>
    <dc:date>2022-03-03T10:05:39Z</dc:date>
    <item>
      <title>Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32410#M23610</link>
      <description>&lt;P&gt;For stability, I've stuck with LTS. Last Friday my containers stopped working with error message:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Py4JException: An exception was raised by the Python Proxy. Return Message: Traceback (most recent call last):
  File "/databricks/spark/python/lib/py4j-0.10.9-src.zip/py4j/java_gateway.py", line 2442, in _call_proxy
    return_value = getattr(self.pool[obj_id], method)(*params)
  File "/databricks/python_shell/dbruntime/pythonPathHook.py", line 45, in initStartingDirectory
    os.chdir(directory)
FileNotFoundError: [Errno 2] No such file or directory: '/Workspace/Repos/Git-repos/'&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;After spending hours and hours of troubleshooting and nothing working, I went for runtime 10.2 (the non-LTS -version), which does not have this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It looks like a regression problem to me. JRE got updated for sure (Log4J-fixes) and this inability to run containers wasn't properly covered with automated tests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas how to get past the error? As this error happens before Python, there is very little I can do to fix this in my container.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 07:46:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32410#M23610</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-01-03T07:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32411#M23611</link>
      <description>&lt;P&gt;First time I see that error but you can try disable/enable repos in admin settings in your databricks workspace&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 11:00:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32411#M23611</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2022-01-03T11:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32412#M23612</link>
      <description>&lt;P&gt;If I disable repos, from where do my notebooks come from?&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 11:05:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32412#M23612</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-01-03T11:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32413#M23613</link>
      <description>&lt;P&gt;I thought just for test to check is it help. Maybe re-enabling it will recover structure.&lt;/P&gt;&lt;P&gt;Additionally that error looks like git is disabled...&lt;/P&gt;&lt;P&gt;(notebooks come from workspace or git repo which is part of workspace)&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 11:12:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32413#M23613</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2022-01-03T11:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32414#M23614</link>
      <description>&lt;P&gt;On a second thought, your idea is something I might try. However, by using a newer bricks node -version the problem dissolves. Mind you, I've been using LTS-node since May 2021 without problems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All this leaves me conflicted. Should I reconnect the git-repo  and see if that would help or ignore the fact LTS-version is unusable with Python-containers and keep my current compute-configuration.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jan 2022 12:13:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32414#M23614</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-01-03T12:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32415#M23615</link>
      <description>&lt;P&gt;@Jari Turkia​&amp;nbsp;- Checking in to see how it went. &lt;/P&gt;</description>
      <pubDate>Fri, 14 Jan 2022 17:51:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32415#M23615</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-01-14T17:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32416#M23616</link>
      <description>&lt;P&gt;This is getting worse. Now JDBC write to SQL is failing for same reason. I haven't yet found a solution for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Am I not supposed to use containers? Python?&lt;/P&gt;&lt;P&gt;This is not cool. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 08:12:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32416#M23616</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-01-19T08:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32417#M23617</link>
      <description>&lt;P&gt;We need detail log what's is happening inside to troubleshoot this. Do you have our support access?&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2022 04:38:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32417#M23617</guid>
      <dc:creator>Atanu</dc:creator>
      <dc:date>2022-01-26T04:38:17Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32418#M23618</link>
      <description>&lt;P&gt;No. All I have is access to Azure with Bricks in it.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2022 07:33:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32418#M23618</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-01-26T07:33:59Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32420#M23620</link>
      <description>&lt;P&gt;Long time has passed and I have a solution to get things working. I do have the logs, but haven't really paid much attention to this lately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To me, this is  a regression issue in Azure Databricks. When a new version of a node is released, it should be tested with containers too. If old node versions are not, maybe I should be informed about it.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2022 10:05:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32420#M23620</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-03-03T10:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Azure Databricks container runtime broken in 9.1 LTS, how to fix?</title>
      <link>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32422#M23622</link>
      <description>&lt;P&gt;Latest node version seems to work for me. Choosing different containers wasn't a factor, the problem was with LXC. I haven't done any follow-up on this, also my containers are custom, see my pull request &lt;A href="https://github.com/databricks/containers/pull/73" target="test_blank"&gt;https://github.com/databricks/containers/pull/73&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2022 12:45:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/azure-databricks-container-runtime-broken-in-9-1-lts-how-to-fix/m-p/32422#M23622</guid>
      <dc:creator>HQJaTu</dc:creator>
      <dc:date>2022-03-03T12:45:56Z</dc:date>
    </item>
  </channel>
</rss>

