<@U088WCP3B4P> - I'm trying to install the cli for...
# ask-elementary-ai
r
@kapa.ai - I'm trying to install the cli for snowflake and I'm using anaconda. can you help me with the steps?
k
A message from kapa.ai
Certainly! Here are the steps to install the Elementary CLI for Snowflake, adapted for use with Anaconda, based on the official documentation and community guidance: 1. Create and Activate a New Conda Environment (Recommended) - This helps isolate dependencies and avoid conflicts.
Copy code
bash    conda create -n elementary-env python=3.9    conda activate elementary-env
Elementary supports Python versions 3.9 - 3.12, so you can choose any supported version for your environment [Quickstart: Elementary CLI](https://docs.elementary-data.com/oss/quickstart/quickstart-cli). 2. Install Elementary CLI with Snowflake Support - Use pip (inside your conda environment) to install the CLI and Snowflake dependencies:
Copy code
bash    pip install 'elementary-data[snowflake]'
This command installs both the core CLI and all required dependencies for Snowflake [CLI install & configure](https://docs.elementary-data.com/oss/cli-install). 3. Validate the Installation - Run the following command to ensure the CLI is installed and accessible:
Copy code
bash    edr --help
If you see the help output, the installation was successful. If you get a "command not found" error, check your PATH or refer to the troubleshooting guide linked in the docs. 4. Configure Your Connection Profile - Elementary requires a dbt-style
profiles.yml
file with a profile named
elementary
. Place this file in your home directory under
.dbt/profiles.yml
. You can generate a template using:
Copy code
bash    dbt run-operation elementary.generate_elementary_cli_profile
Then fill in your Snowflake credentials as shown in the documentation [Generate observability report](https://docs.elementary-data.com/oss/guides/generate-report-ui). 5. (Optional) Additional Configuration - You can add a
config.yml
in
~/.edr/
for further customization, but this is optional. Note: If you encounter missing dependencies or module errors, ensure you are installing with pip inside your activated conda environment, and that your environment’s Python version is supported. If you need to install dbt or other dependencies, do so within the same environment to avoid conflicts. Let me know if you need help with the
profiles.yml
configuration or run into any issues!
r
@kapa.ai - When I run edr report command. I'm getting the below error
Copy code
2025-08-22 11:12:31 — INFO — Running with edr=0.19.4
INFO:elementary.cli.cli:Running with edr=0.19.4
2025-08-22 11:12:31 — INFO — Installing packages for edr internal dbt package...
INFO:elementary.clients.dbt.command_line_dbt_runner:Installing packages for edr internal dbt package...
2025-08-22 11:12:31 — INFO — Running dbt command --log-format json deps --project-dir /opt/anaconda3/lib/python3.11/site-packages/elementary/monitor/dbt_project
INFO:elementary.clients.dbt.command_line_dbt_runner:Running dbt command --log-format json deps --project-dir /opt/anaconda3/lib/python3.11/site-packages/elementary/monitor/dbt_project
zsh: killed     edr report
Can you help me fix it?
k
A message from kapa.ai
The error message
zsh: killed     edr report
during the
edr report
command, especially after the log line about running
dbt ... deps
, strongly suggests that the process is being killed by the operating system. This is commonly due to the process exceeding available memory (an "out of memory" or OOM issue), which causes the OS to forcibly terminate it. This pattern has been reported by several users in the Elementary community, and the recommended solution is to increase the memory (and possibly CPU) available to the environment where you are running the command. This is especially common in environments like containers, VMs, or systems with limited resources. See similar issues and solutions discussed here: - "The error you’re seeing, ... died with <Signals.SIGKILL: 9> means that the dbt process was forcibly killed. Signal SIGKILL (9) is typically sent when a process exceeds available resources or is manually killed. ... Can you try increasing memory/cpu?" [Slack thread: ECS/container memory issue](https://slack.com/archives/C02CTC89LAX/p1729498047922669) - "I looked for the error you got: died with <Signals.SIGKILL: 9>. and it looks like the most common cause is out of memory issue. Is it possible that your machine runs out of memory?" [Slack thread: OOM on Cloud Run](https://slack.com/archives/C02CTC89LAX/p1711457384233159) What you should do: 1. Increase available memory for your Anaconda environment or the system where you are running
edr report
. If you are running inside a container or VM, allocate more RAM. 2. Close other memory-intensive applications to free up resources. 3. Try running the command again after increasing resources. If the problem persists after increasing memory, please check for any permission issues or installation problems, but the overwhelming evidence from the knowledge sources points to an out-of-memory issue as the root cause. Let me know if you need help with steps to increase memory or further troubleshooting!