If you try using relative pathes from git together with environment-variables from stack.env you end up with the following:
an error occurred while running unpacker container with exit code 255: open /mnt/portainer-mounts/foo/bar/portainer-compose-unpacker/stacks/bar/bar/stack.env: no such file or directory
The unpacker seems to take docker-compose.yml env_file: stack.env and adds it to its list-of-files to verify or so?
It does not exist of course, so we run into a failure deploying the stack
Adding the file to git will end up overwriting the values set in Portainer UI.
If you try using relative pathes from git together with environment-variables from stack.env you end up with the following:
The unpacker seems to take docker-compose.yml
env_file: stack.envand adds it to its list-of-files to verify or so? It does not exist of course, so we run into a failure deploying the stackAdding the file to git will end up overwriting the values set in Portainer UI.