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:
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
- Create stack with services with labels
- Start stack
- stop stack
- Remove service
- Try to start stack
- See error
Relevant Logs
Compose
Additional Context
No response
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:
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.ymlfile, 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
Relevant Logs
Compose
Additional Context
No response