Open FoxxMD opened 3 months ago
As dockge is running in a container it's $HOME is different from your hosts $HOME not sure how this could be avoided other than you setting the env var of $HOME for dockge to your users home path.
But this is not something I would recommend
⚠️ Please verify that this bug has NOT been reported before.
🛡️ Security Policy
Description
ENVs inside the dockge container seem to be overwriting ENVs not explicitly specified in
.env
for a stack. Dockge should only be using ENVs from the host OS + whatever is specified in .env file or in the compose file itself.Note that this could sort of be fixed by global environmental variables (PR 387) but ideally it shouldn't be required to fix this issue.
👟 Reproduction steps
Assuming your user on the host is
foo
the$HOME
env should be/home/foo
./config
)- $HOME/myData:/config
👀 Expected behavior
On the host we observe that
/home/foo/myData
is created😓 Actual Behavior
On the host we observe that
/home/node/myData
is created instead.node
is the user for the dockge container and in the container$HOME
is exported asHOME=/home/node
(check my exec'ing in and runningprintenv -0
.Dockge Version
1.4.2
💻 Operating System and Arch
EndevourOS (Arch) Kernel 6.10.0-arch1-2
🌐 Browser
Firefox 128.0.2
🐋 Docker Version
Docker 27.0.3
🟩 NodeJS Version
No response
📝 Relevant log output