Thanks for the detailed write-up. Short answer: your workflow is possible, but installing/running Lakebridge from a Databricks serverless web terminal is not the recommended path today.

The error you’re seeing happens because Lakebridge installation expects to create its own Python virtual environment, and serverless web terminal environments are too restricted for that in many cases.

What should work instead:

• export the Snowflake DDL/SQL files

• run Lakebridge from a machine you control (local machine, VM, jump box, or container runner)

• write the converted output back to Databricks

• use a Databricks job/workflow to execute the migrated scripts afterward

A few notes:

• Your Snowflake → Lakebridge → Databricks flow is a valid use case.

• Snowflake is supported as a transpile source.

• If you want to run Lakebridge inside Databricks anyway, the better workaround is a dedicated all-purpose / single-user cluster rather than serverless web terminal.

So my recommendation is: keep the Lakebridge runtime outside the restricted serverless environment, and use Databricks for orchestration and execution of the converted output.