Describe the bug
-
content in dagu/base.yaml:
env:
- QUANT_SIGNAL_DIR: "/work/quant-signal"
-
content in dags/health-check.yaml:
working_dir: ${QUANT_SIGNAL_DIR}
steps:
- command: printenv QUANT_SIGNAL_DIR PYTHON_BIN
-
content in /work/quant-signal/.env:
PYTHON_BIN=/usr/local/bin/python
When I run the DAG pipeline, it's supposed to print "/work/quant-signal" and "/usr/local/bin/python". And It works when using dagu_2.6.7_linux_arm64.tar.gz. However, when using dagu_2.6.7_linux_amd64.tar.gz, it only prints "/work/quant-signal", which means it didn't parse the .env file in the working_dir.
To Reproduce
Steps to reproduce the behavior:
- Use dagu_2.6.7_linux_amd64.tar.gz
- setup DIR environment variable in base.yaml
- setup .env file in DIR folder
- setup working_dir and printenv in dags/workflow.yaml
- Run the workflow
- See error of printenv
Environment
- Dagu version: dagu_2.6.7_linux_amd64
- OS: Debian 12.5
- Installation method: download binary
Screenshots

Describe the bug
content in dagu/base.yaml:
env:
- QUANT_SIGNAL_DIR: "/work/quant-signal"
content in dags/health-check.yaml:
working_dir: ${QUANT_SIGNAL_DIR}
steps:
- command: printenv QUANT_SIGNAL_DIR PYTHON_BIN
content in /work/quant-signal/.env:
PYTHON_BIN=/usr/local/bin/python
When I run the DAG pipeline, it's supposed to print "/work/quant-signal" and "/usr/local/bin/python". And It works when using dagu_2.6.7_linux_arm64.tar.gz. However, when using dagu_2.6.7_linux_amd64.tar.gz, it only prints "/work/quant-signal", which means it didn't parse the .env file in the working_dir.
To Reproduce
Steps to reproduce the behavior:
Environment
Screenshots