Delete stack failed to create env file

[illspirit]

Ask a Question!

Hello, I'm getting the error failed to "create env file: open /data/compose/7/stack.env: no such file or directory" when trying to delete a stack. I've tried putting a stack.env file in that location but I'm not having any luck. Is there a way to force delete a stack?

I've seen this question asked a couple times and everyone says to make a new file and it's just not working for me.

[Nick-Portainer]

Hey,

When you say you are not having any luck, is this in terms of not being able to add the env file into that location?

[june012006]

This bug still persists. I'm experiencing it myself. I've already touched the file it's looking for and it still gives the same inane error

[Nick-Portainer]

Do you have a way of replicating this, so I can test?

[jakemauer]

Chiming in to say I'm having this problem with a specific stack. It's using a compose file via a git repo that is most definitely accessible as every other stack I have is using compose files from the same repo.

1. When I open the stack's management page I get an error: "Failure: Could not get the contents of the file 'server-utilities.yml'
2. When I click "Stop this Stack" or "Delete this Stack" I get:

Failure
Failed to create env file: open /data/compose/8/f9bbcae05749d4be9f0304d7c4233bea6b45b905/stack.env: no such file or directory

[Nick-Portainer]

So confirming, this is just one specific stack, you have others in the exact same config besides the image and they all work fine? What is the image that is failing, can you share the compose so I can try replicate?

Are you using Github?

[jakemauer]

I'm using a local instance of gitea for my compose files. I ended up creating the folder and an empty stack.env file at the location presented in the error and I was then able to stop and then delete the stack. After which I recreated it and it has been fine since.