Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENH] - Allow any env vars to be passed through environment yaml spec #826

Open
kcpevey opened this issue May 28, 2024 · 0 comments
Open
Assignees

Comments

@kcpevey
Copy link
Contributor

kcpevey commented May 28, 2024

Feature description

Right now we only allow the GPU-specific environment variable. However, conda allows the setting of any env var inside an environment via the yaml spec - https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#setting-environment-variables

It would be nice to be able to set any environment variable.

Valid example:

channels:
  - conda-forge
dependencies:
  - pytorch
  - ipykernel
variables:
  CONDA_OVERRIDE_CUDA: "12.0"

Value and/or benefit

  • Improve UX, reduce confusion when users see that the yaml spec has the option to add env vars
  • Improve feature parity between conda-store and local conda usage (which is what users are comfortable with)

Anything else?

This was originally reported on nebari - nebari-dev/nebari#2445

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New 🚦
Development

No branches or pull requests

2 participants