Skip to content

[Bug]: docker-compose.override.yml is not updated when removing a container #51

@Joly0

Description

@Joly0

Version

2026.02.24

Unraid Version

7.2.4

Bug Description

I manage my arr-stack with compose and have just tried to remove two services from that stack (huntarr and shelfarr). I didnt bother about this "issue" when i removed huntarr, but for shelfarr i am now creating this bug report.

So the problem is, when i stop my stack and remove a container that previously had for example a webui or an icon set via the webui labels, i cannot start the stack anymore, i only get this error:

Image

Afterwards i checked the stacks project folder in the /boot/config/plugins/compose.manager/projects/arr-stack/ folder and noticed in the docker-compose.override.yml file, that the shelfarr labels are still there. I am not 100% certain (didnt check) but i think this was not a problem with the previous version of the compose plugin (i mean the version this here is forked from)

Expected Behavior

File should be properly updated, so i can start my stack without having to fiddle with that file.

Steps to Reproduce

  1. Create stack with services with labels
  2. Start stack
  3. stop stack
  4. Remove service
  5. Try to start stack
  6. See error

Relevant Logs

Compose

Additional Context

No response

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions