You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docker run -v $(pwd)/data:/data --env-file .env --rm -it transaction-latency
82
83
```
83
84
85
+
### Note about .env file loading
86
+
87
+
When running with Docker, you may see the log message:
88
+
```
89
+
Error loading .env file
90
+
```
91
+
92
+
This is expected and harmless. The application uses two methods to load environment variables:
93
+
1.**Docker's `--env-file` flag** (recommended): Sets environment variables at container runtime
94
+
2.**Direct .env file loading**: Attempts to read the `.env` file from inside the container
95
+
96
+
Since we use the `--env-file` approach for security (keeping secrets out of the image), the direct file loading fails but the environment variables are still available via Docker. The application continues normally and all configuration works as expected.
97
+
84
98
## Results
85
99
86
100
After completion, results are saved to the `./data/` directory:
0 commit comments