topic Re: Access the environment variable from the custom container base cluster in Machine Learning

Access the environment variable from the custom container base cluster

lukaszl — Thu, 12 Jan 2023 10:15:05 GMT

Hi Databricks Community,

I want to set environment variables for all clusters in my workspace. The goal is to the have environment variable, available in all notebooks executed on the cluster.

The environment variable is generated in global init script and stored in the `/etc/environment` like documented here: https://community.databricks.com/s/question/0D58Y000096UKm5SAG/set-environment-variables-in-global-init-scripts

After my init script execution the `/etc/environment` content looks like:

CLUSTER_DB_HOME=/databricks
DATABRICKS_RUNTIME_VERSION=10.4
DB_HOME=/databricks
DEFAULT_DATABRICKS_ROOT_VIRTUALENV_ENV=/databricks/python3
MLFLOW_CONDA_HOME=/databricks/conda
MLFLOW_PYTHON_EXECUTABLE=/databricks/python/bin/python
MLFLOW_TRACKING_URI=databricks
PYARROW_IGNORE_TIMEZONE=1
export MY_TEST_VAR=test

The integration is working for the standard clusters and I can use the variable in the notebooks.

BUT for the clusters with defined custom docker container, the environment variable is invisible.

With the custom docker container cluster, I mean the clusters with the option "Use your own Docker container" set. For that type of clusters I can't access the environment variable. E.g the result of the code

import os
print(os.getenv('MY_TEST_VAR'))

is empty (None).

Any ideas where do I need to store environment variables to have them available in all cluster types?

Thank you!

Re: Access the environment variable from the custom container base cluster

-werners- — Thu, 12 Jan 2023 10:26:45 GMT

I suppose in the dockerfile of your image.

Re: Access the environment variable from the custom container base cluster

lukaszl — Fri, 13 Jan 2023 11:15:21 GMT

Thank you for the quick answer!

Unfortunately, I'm going to store the dynamic access token value in that environment variable. The token need to be generated per cluster and will expire in 4 hours. So my environment variable value is known only on cluster setup. That is the reason why I used the init script. So the docker image creation will be to early.

Does Databricks have the environment variable storage which will be injected before each notebook run? That will be the perfect solution for me.

Re: Access the environment variable from the custom container base cluster

-werners- — Fri, 13 Jan 2023 13:48:44 GMT

there is spark conf which you can set on cluster creation or even in the notebook.

No idea how that would work in docker though.

Re: Access the environment variable from the custom container base cluster

lukaszl — Mon, 16 Jan 2023 09:19:52 GMT

Thank you @Werner Stinckens !

Based on your suggestion I found the Databricks internal file

/databricks/spark/conf/spark-env.sh

which is containing the environment variables visible in the notebook. Adding the new variable over this file solves my problem.

Re: Access the environment variable from the custom container base cluster

grazie — Mon, 23 Jan 2023 20:41:42 GMT

Thanks @Lukasz Lu - that worked for me as well. When I used the following script:

#!/bin/bash
echo MY_TEST_VAR=value1 | tee -a /etc/environment >> /databricks/spark/conf/spark-env.sh

for non-docker clusters, MY_TEST_VAR shows up twice in ` /databricks/spark/conf/spark-env.sh`
for docker clusters MY_TEST_VAR shows up once
in both cases `os.getenv("MY_TEST_VAR")` gives value1 as expected

Re: Access the environment variable from the custom container base cluster

Sahil0007 — Tue, 06 May 2025 05:19:28 GMT

where I have to use this script ?