[BUG] - Setting env vars in conda store doesn't work in 2024.4.1 Nebari

[Adam-D-Lewis]

Describe the bug

I created this scratch environment

I tried seeing if PYTHONUSERBASE was set after activating scratch and it wasn't set.

I'm not sure if the issue is in conda store config in Nebari or upstream in conda store.

Expected behavior

Env var should be set

OS and architecture in which you are running Nebari

Linux x86-64

How to Reproduce the problem?

see above
Nebari version - 2024.4.1

Command output

No response

Versions and dependencies used.

No response

Compute environment

None

Integrations

No response

Anything else?

No response

[kcpevey]

@Adam-D-Lewis just to confirm - the same process works on your local machine with just conda?

[Adam-D-Lewis]

Yes, it works for me locally (not using conda store, but just using a conda environment.yaml). Here's a reference https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#setting-environment-variables

[kcpevey]

@Adam-D-Lewis the only environment variable available to users is the GPU-specific variable, CONDA_OVERRIDE_CUDA.

I've opened an issue on conda-store to allow any environment variable to be passed (feature parity with conda). I'll close this as it will need to be fixed at the conda-store level.

[gabalafou]

Cross-reference:

• Allow passing variables via raw YAML conda-incubator/conda-store-ui#354