This message was deleted.

The error message you're encountering indicates that the

DAGSTER_HOME

environment variable is not set. Dagster relies on this environment variable to locate the directory where it should store instance-related data, such as run history and event logs. This directory also typically contains the

dagster.yaml

configuration file. To resolve this error, you need to set the

DAGSTER_HOME

environment variable to point to a directory on your filesystem where you want Dagster to store its instance data. Here's how you can do this for different operating systems: For Unix-like systems (e.g., Linux, macOS):

sh export DAGSTER_HOME="/path/to/dagster_home"

For Windows using PowerShell:

powershell $env:DAGSTER_HOME = "C:\path\to\dagster_home"

For Windows using Command Prompt:

cmd set DAGSTER_HOME=C:\path\to\dagster_home

Make sure to replace

/path/to/dagster_home

or

C:\path\to\dagster_home

with the actual path to the directory you want to use for your Dagster instance. After setting the

DAGSTER_HOME

environment variable, you can try running the

dagster run wipe

command again, and it should work without throwing the

DagsterHomeNotSetError

. If you do not want to persist data across sessions and are okay with using a temporary directory for storage that is cleaned up when the process exits, you can use

DagsterInstance.ephemeral()

in your code to create a transient instance. However, this is typically used for temporary local development or testing.