* This issue is similar to #827 in that both are related to enviromental variable setting.
* We can temporaly avoid this problem by using the `env_file` statement in `compose.yml`
_To help debug the issue as quickly as possible, we recommend generating a support bundle with `finch support-bundle generate` and attaching it to this issue. This packages all Finch-related configs and logs into one file._
[finch-support-20240407232422.zip](https://github.com/runfinch/finch/files/14897562/finch-support-20240407232422.zip)
Describe the bug Cannot use
--env-file
option withfinch compose up
commandsoftware version finch: 1.1.3 MacOS: Sonoma 14.4.1
Steps to reproduce
services: show-env: command:
Expected behavior The busybox container executes
env
command, and the container stops. The standard output may be like as followsScreenshots or logs
Actual result
Additional context
finch compose run
(notup
) command was successfully executed, and environment variables (A=1
,B=2
) were set.INFO[0000] Ensuring image busybox INFO[0000] Creating container test-show-env-run-7d8df8b0049e PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin B=2 A=1 TERM=xterm HOME=/root INFO[0000] Stopping containers (forcibly) INFO[0000] Stopping container test-show-env-run-7d8df8b0049e