Changing the env value in env file edit section does not trigger container recreation.

[Janczykkkko]

⚠️ 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

In the scope of a stack, while editing it, changing the value of a variable in the env file field, then deploying does not recreate the container using that var, therefore its still using the old value.
In my case the env var is used to specify bind mount on host i.e. - ${AUDIOBOOKS}:/audiobook:ro
I AM NOT SURE THIS IS SUPPOSED TO BE THIS WAY, I BELIEVE PORTAINER DOES IT THIS WAY.

My first bug report ever, be gentle :)

👟 Reproduction steps

Create any stack with at least one container using an env var as bind mount path on host.
Set the var value in .env portion of stack editing.
Deploy.
Edit and change just the value of the variable in the .env portion of edit.
Deploy
Change did not take effect i.e. container is using the old var value.

👀 Expected behavior

The container using the env var is recreated for changes to take effect.

😓 Actual Behavior

The changes don't take effect unless stack is recreated or the container itself is recreated.

Dockge Version

1.4.0

💻 Operating System and Arch

Ubuntu 23.04

🌐 Browser

n/a

🐋 Docker Version

Docker version 24.0.7, build afdd53b

🟩 NodeJS Version

No response

📝 Relevant log output

none

[syko9000]

I can't replicate this on macos using the same docker version, so it might be a OS thing. If you edit the .env manually and docker compose up -d do the services still not restart?