Can't delete stack if compose.yml has some error in it

[Nostang3]

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

I started to create a stack but decided I didn't want it so I tried to delete it. Never deployed it. It wouldn't let me because it looks like it tries to validate the text before allowing me to delete it. It still had some <insert/path/here:/path/to/folder> entries.

👟 Reproduction steps

1. Paste in some default compose

services:
  tinymediamanager:
    image: tinymediamanager/tinymediamanager:latest
    container_name: tinymediamanager
    environment:
      - USER_ID=1000
      - GROUP_ID=100
      - ALLOW_DIRECT_VNC=true
      - LC_ALL=en_US.UTF-8 # force UTF8
      - LANG=en_US.UTF-8   # force UTF8
      - PASSWORD=<password>
    volumes:
      - </path/to/local/data/>:/data
      - </path/to/movies>:/media/movies
      - </path/to/addons/>:/media/tv_shows
    ports:
      - 5900:5900 # VNC port
      - 4000:4000 # Webinterface
    restart: unless-stopped

2. Save.
3. Attempt to delete.

👀 Expected behavior

Would like to delete the file without having to check if the compose is valid. If I don't want to the stack it shouldn't need to be valid unless I'm missing something.

😓 Actual Behavior

Fails to delete with error.

Dockge Version

1.4.2

💻 Operating System and Arch

Trunas Custom App

🌐 Browser

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:133.0) Gecko/20100101 Firefox/133.0

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

service "tinymediamanager" refers to undefined volume </path/to/local/data/>: invalid compose project

[christmaswreath]

Same issue here. "validating /opt/stacks/aio/compose.yaml: services.nextcloud-aio-mastercontainer.environment.0 must be a string"

Stacks don't appear in Portainer, what gives?

[DomiiBunn]

As a simple solution.

Remove the stacks folder

[christmaswreath]

You can also just replace the compose.yaml with a working one and then delete the stack. Still, it would be nice to be able to delete a “stack” with no compose.yaml and .env or one that doesn’t work.

[DomiiBunn]

@christmaswreath I agree.

Though this can cause an issue of hanging containers.

[F1zzyD]

Yep, having this issue as well. Can't delete it, change it, or anything if Dockage gets confused. It says it's maintaining it and inactive, but for some reason has no control over a stopped or ended container...