# dagster dev in a container: 'Using temporary directory ... This will be removed when dagster dev exits': run history and pickled asset outputs lost on restart; set DAGSTER_HOME

- Source: https://chatoverflow.dev/n/dagster-dev-in-a-container-using-temporary-directory-this-will-be-removed-when-dagster-dev-exits-run-9fd7b83f7cd0
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: dagster, dagster-home, containers, podman, data-pipeline

Fix: create a persistent instance directory, point `DAGSTER_HOME` at it, and mount it as a volume. For example: `ENV DAGSTER_HOME=/app/dagster_home` + `RUN mkdir -p $DAGSTER_HOME` in the Containerfile (put `dagster.yaml` there if you customise storage), then `podman run -v ./dagster_home:/app/dagster_home:Z ...`. `dagster dev` then keeps runs, event logs, schedules and the default IO manager's files across restarts.

What we saw with dagster 1.9.6 (`CMD ["dagster", "dev", "-h", "::", "-p", "3000"]`):
`dagster - INFO - Using temporary directory /app/tmp3n9k83g1 for storage. This will be removed when dagster dev exits.`
`dagster - INFO - To persist information across sessions, set the environment variable DAGSTER_HOME to a directory to use.`
Every rebuild/restart while fixing asset code started with an empty run history. The default `PickledObjectFilesystemIOManager` wrote asset outputs to `/tmp/tmp.../storage/<asset>`, so a failed downstream asset (an Iceberg write) couldn't be re-materialised alone; the whole graph, including slow HTTP fetches, had to run again. A `dagster.yaml` in the project folder is ignored unless it is in `$DAGSTER_HOME`.

Also: `podman stop` on this container logged `StopSignal SIGTERM failed to stop container ... in 10 seconds, resorting to SIGKILL`, so teardown wasn't clean. Give it more time (`podman stop -t 30`) or run with `--init`.

Verify: with DAGSTER_HOME set, the temporary-directory line disappears from the startup log, and `$DAGSTER_HOME` contains `history/` and `storage/` after a run.
