Unable to delete stack : failed to create env file: open /data/compose/234/stack.env: no such file or directory

[ptempier]

Bug description
Go to stack click delete this tack , get error :
failed to create env file: open /data/compose/234/stack.env: no such file or directory

Expected behavior
The stack is deleted

Portainer Logs
The problem does not appears in the server or agent logs
But is seems to be a server error, not a browser or agent error.

Here's the complete notification :

Error | Failure | failed to create env file: open /data/compose/248/stack.env: no such file or directory
Error | Failure | could not get the contents of the file 'docker-compose.yml'

Steps to reproduce the issue:
Not sure what the user did.
There are env variable sets, but the stack is saved with no docker-compose showing in the editor.

Technical details:

• Portainer version: Portainer Business Edition 2.18.2
• Docker version (managed by Portainer): 20.10.23
• Platform (windows/linux): Fedora release 37
• Command used to start Portainer : docker run -d -p zzz:9443 -p zzz:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /data/containers/portainer/:/data -v /data/containers/portainer/certs/:/certs portainer/portainer-ee:latest --sslcert /certs/zzz --sslkey /certs/zzz
• Browser: chrome
• Use Case : self service for peoples to train to use containers
• Have you reviewed our technical documentation and knowledge base? Yes

** Notes :
Manually creating the problematic folder on the host solves the issue,
but signaling the issue anyway in the hope to get a proper upstream fix.

[samdulam]

@ptempier
Have seen this happen on a rare occasion. And workaround is the same as what you have done.
I'll flag this with the Product team.. May be we could have a force delete option

[oliverbooth]

I am now getting this issue. Creating the folder on the host does not solve the issue.

[tugdualenligne]

Same issue. I stupidly deleted directly from the host, instead of doing it through Portainer, and now, even i f I recreate the folder and files, I can't delete the stack from Portainer
If anyone has an idea to solde that... (very small issue, I agree ;-)

[Daronsong]

are there any updates to this?

[leikoilja]

Have the same issue after having a GIT connected stack, changing some volume binding configuration in the docker-compose file and then 'redeploying' the stack. got error during redeployment so containers went off, now the stack is stuck in the loop:
"failed to create env file: open...", can't delete it