.env data not being parsed by docker #63

New issue

Closed

opened 2026-02-20 13:10:13 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 13:10:13 -05:00

Owner

Originally created by @markhaines on GitHub (Dec 8, 2023).

⚠️ Please verify that this bug has NOT been reported before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

If I move lines from Environment part of the yaml and move them to the .env config pane instead (stripping out - etc so correctly formatted) I've noticed that Dockge ignores them when starting the container, and so the container fails to start.

👟 Reproduction steps

Example container 'adguardhome-sync' refuses to start if the environment: variables are not part of the main config.

👀 Expected behavior

Docker should read the .env config and launch the container including them.

😓 Actual Behavior

Docker fails to read them

Dockge Version

1.3.2

💻 Operating System and Arch

Alma 9.3

🌐 Browser

Chrome

🐋 Docker Version

24.0.7

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @markhaines on GitHub (Dec 8, 2023). ### ⚠️ Please verify that this bug has NOT been reported before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/dockge/security/policy) ### Description If I move lines from Environment part of the yaml and move them to the .env config pane instead (stripping out - etc so correctly formatted) I've noticed that Dockge ignores them when starting the container, and so the container fails to start. ### 👟 Reproduction steps ![Screenshot 2023-12-08 at 15 03 50](https://github.com/louislam/dockge/assets/1022008/c3b9916f-2f4b-4a16-9e9f-ef92c117caa1) Example container 'adguardhome-sync' refuses to start if the environment: variables are not part of the main config. ### 👀 Expected behavior Docker should read the .env config and launch the container including them. ### 😓 Actual Behavior Docker fails to read them ### Dockge Version 1.3.2 ### 💻 Operating System and Arch Alma 9.3 ### 🌐 Browser Chrome ### 🐋 Docker Version 24.0.7 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-20 13:10:13 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-20 13:10:16 -05:00

Author

Owner

@chris-lsn commented on GitHub (Dec 8, 2023):

You've to specify the env_file property to the container
https://docs.docker.com/compose/environment-variables/set-environment-variables/#use-the-env_file-attribute

adguardhome-sync:
  env_file:
    - .env

@chris-lsn commented on GitHub (Dec 8, 2023): You've to specify the `env_file` property to the container https://docs.docker.com/compose/environment-variables/set-environment-variables/#use-the-env_file-attribute ```yaml adguardhome-sync: env_file: - .env ```

deekerman commented

2026-02-20 13:10:16 -05:00

Author

Owner

@markhaines commented on GitHub (Dec 8, 2023):

Ah, I see... 😳

@markhaines commented on GitHub (Dec 8, 2023): Ah, I see... 😳