I’m following the “Create New Project” steps here https://docs.dagster.io/getting-started/create-new-project and step 3 doesn’t work. Running

dagster-daemon run

resulted in this error

dagster-daemon run
Traceback (most recent call last):
  File "/usr/local/bin/dagster-daemon", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/dagster/daemon/cli/__init__.py", line 126, in main
    cli(obj={})  # pylint:disable=E1123
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/dagster/daemon/cli/__init__.py", line 32, in run_command
    raise Exception(
Exception: dagster-daemon can't run using an in-memory instance. Make sure the DAGSTER_HOME environment variable has been set correctly and that you have created a dagster.yaml file there.

Hey Ming! Does this error show up even after you set

$DAGSTER_HOME

to a directory path and create a

dagster.yaml

in that directory?

The solution is to set

DAGSTER_HOME

IMO it should default to

export DAGSTER_HOME=`pwd`

if it’s not already set

That's a good suggestion!

Another problem with the tutorial is the generated sensor and pipeline mode is not compatible.

my_pipeline

has modes

dev

and

test

, but

my_sensor

defaults to mode

default

resulting in run time error

cc @sandy for approachability and tutorial feedback

@alex thoughts on whether we could enable running the daemon without setting dagster_home?

it only functions with a consistent instance shared amongst other running components so it requires DAGSTER_HOME

I created these two scripts to make running locally.

dagit.sh

#!/usr/bin/env bash
mkdir -p .dagster
export DAGSTER_HOME=`pwd`/.dagster
exec dagit -h 0.0.0.0

dagster-daemon.sh

#!/usr/bin/env bash
mkdir -p .dagster
export DAGSTER_HOME=`pwd`/.dagster
exec dagster-daemon run

Hope this is help to others.