13 hours ago, mdastous said:

were you able to reproduce the pull issue?

Yes, this is fixed in dev, I'll be releasing into beta soon.

Just updated to 2026.07.02 a couple days ago. Two issues I've noticed:

1. In the new "Columns" view customization, if any changes are made, clicking "Cancel" still saves the changes and closes the box

2. I have an Immich stack installed that has been working perfectly fine. It is still functional, but I see the following error in my logs:

   1. Jul 16 20:39:53 unRAID compose.manager: [WARN] [composeLoadlist] progressive stack load failed - Data: {"project":"immich","position":1,"total":3,"elapsedMs":338}

      Jul 16 20:39:53 unRAID compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":2,"elapsedMs":673,"mode":"progressive","composeListReady":true}

I'm trying to setup Arcane for docker management. Now I have it working with the compose manger plugin. But I am a bit confused. I want to build the "stack" inside of Arcane not the compose manager. I really just want to use the compose manager to run the initial Arcane yaml.

So would my yaml file just be for Arcane and nothing else? And the .env file that I put in there is that going to apply to just Arcane or all the containers that I spin up using it as well?

/mnt/user/appdata/docker-compose/arcane/compose.yaml

I have my projects folder setup as

PROJECTS_FOLDER="/mnt/user/appdata/docker-compose/

And I would have thought that Arcane wouldn't be able to see anything below there but when it loaded it showed all my of existing containers that reside in the /mnt/user/appdata//appdata folder.

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - arcane-data:/app/data
      - /mnt/user/appdata/docker-compose/arcane:/app/data
      
volumes:
  arcane-data:
  

On 7/20/2026 at 12:59 AM, GorOps said:

I'm trying to setup Arcane for docker management. Now I have it working with the compose manger plugin. But I am a bit confused. I want to build the "stack" inside of Arcane not the compose manager. I really just want to use the compose manager to run the initial Arcane yaml.

So would my yaml file just be for Arcane and nothing else? And the .env file that I put in there is that going to apply to just Arcane or all the containers that I spin up using it as well?

/mnt/user/appdata/docker-compose/arcane/compose.yaml

I have my projects folder setup as

PROJECTS_FOLDER="/mnt/user/appdata/docker-compose/

And I would have thought that Arcane wouldn't be able to see anything below there but when it loaded it showed all my of existing containers that reside in the /mnt/user/appdata//appdata folder.

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - arcane-data:/app/data
      - /mnt/user/appdata/docker-compose/arcane:/app/data
      
volumes:
  arcane-data:
  

You mounted the docker socket so it's showing all the dockers running on your server. It's using unraids install of docker, not its own docker in docker setup or something.

Can we edit the env file to update the COMPOSE_VERSION=5.1.2? And where can we do this?

Icons that do not have a custom icon and the default stack icon are broken and flickering fast.

19 hours ago, sportsziggy said:

Icons that do not have a custom icon and the default stack icon are broken and flickering fast.

Yeah, same here

The consol is spamming 404s on this image

Making the page unresponsive after a while.

Unrelated to the plugin, unraid issue

https://product.unraid.net/p/7-3-2-dashboard-nginx-log-spam-from-stale-docker-template-fallback-icons

Having an issue, where my compose stacks show update available, but when I click Update the dialog says the most up to date images are already pulled. Nothing gets updated however and the update available dialog still appears. I've tried clearing the update cache, but doesn't fix the issue. Any ideas?

On 8/8/2026 at 3:33 PM, GorOps said:

Can we edit the env file to update the COMPOSE_VERSION=5.1.2? And where can we do this?

Do you just want to update it to the latest? This needs done by me when the plugin is packaged it grabs whatever version is in there. Its not something you can change at runtime. I'll test updating it to the latest 5.4.0, though I usually like to wait for at least a x.x.1 before updating. AND I've been awol for a bit dealing with life so I haven't had a change to do any updates.

On 8/13/2026 at 12:45 PM, BWPanoramas said:

Having an issue, where my compose stacks show update available, but when I click Update the dialog says the most up to date images are already pulled. Nothing gets updated however and the update available dialog still appears. I've tried clearing the update cache, but doesn't fix the issue. Any ideas?

I'll have a beta out soon that removes the docker.manager update checking as it seems to be a bit unreliable, there is a post here about it. I copied that and fixed a couple things and it is now owned by compose manager so updates that dont exist should be completely fixed going forward. (Once the beta and then the next stable are released)

On 8/14/2026 at 2:57 PM, mstrhakr said:

I'll have a beta out soon that removes the docker.manager update checking as it seems to be a bit unreliable, there is a post here about it. I copied that and fixed a couple things and it is now owned by compose manager so updates that dont exist should be completely fixed going forward. (Once the beta and then the next stable are released)

Look forward to trying it out!

All of a sudden all of my 'compose up' are failing a few seconds after they start pulling the images from dockerhub. These are the logs:

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [stack-action] setStackActionInProgress - Data: {"stack":"immich","inProgress":true,"text":"starting..."}

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [ui-render] processPendingComposeReloads - Data: {"stacks":["immich"]}

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [refreshStackRow] response - Data: {"project":"immich","data":"{\"result\":\"success\",\"containers\":[],\"stackState\":{\"state\":\"stopped\",\"label\":\"stopped\",\"shape\":\"square\",\"color\":\"grey-text\",\"running\":0,\"total\":0},\"projectName\":\"immich\",\"startedAt\":null}"}

Aug 27 11:58:30 Beavertown nginx: 2026/08/27 11:58:30 [error] 14034#14034: *1068 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 100.80.26.1, server: unraid.<my-tailnet-domain>.ts.net, request: "GET /logterminal/compose_manager_action/token HTTP/2.0", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/token", host: "unraid.<my-tailnet-domain>.ts.net", referrer: "https://unraid.<my-tailnet-domain>/logterminal/compose_manager_action/"

Aug 27 11:58:30 Beavertown nginx: 2026/08/27 11:58:30 [error] 14034#14034: *1983 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 100.80.26.1, server: unraid.<my-tailnet-domain>.ts.net, request: "GET /logterminal/compose_manager_action/ws HTTP/1.1", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/ws", host: "unraid.<my-tailnet-domain>.ts.net"

Any idea why this might have started happening?

Edited August 27Aug 27 by castores
redacted my tailnet domain

On 8/27/2026 at 7:35 AM, castores said:

All of a sudden all of my 'compose up' are failing a few seconds after they start pulling the images from dockerhub. These are the logs:

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [stack-action] setStackActionInProgress - Data: {"stack":"immich","inProgress":true,"text":"starting..."}

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [ui-render] processPendingComposeReloads - Data: {"stacks":["immich"]}

Aug 27 11:58:18 Beavertown compose.manager: [INFO] [refreshStackRow] response - Data: {"project":"immich","data":"{\"result\":\"success\",\"containers\":[],\"stackState\":{\"state\":\"stopped\",\"label\":\"stopped\",\"shape\":\"square\",\"color\":\"grey-text\",\"running\":0,\"total\":0},\"projectName\":\"immich\",\"startedAt\":null}"}

Aug 27 11:58:30 Beavertown nginx: 2026/08/27 11:58:30 [error] 14034#14034: *1068 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 100.80.26.1, server: unraid.<my-tailnet-domain>.ts.net, request: "GET /logterminal/compose_manager_action/token HTTP/2.0", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/token", host: "unraid.<my-tailnet-domain>.ts.net", referrer: "https://unraid.<my-tailnet-domain>/logterminal/compose_manager_action/"

Aug 27 11:58:30 Beavertown nginx: 2026/08/27 11:58:30 [error] 14034#14034: *1983 connect() to unix:/var/tmp/compose_manager_action.sock failed (111: Connection refused) while connecting to upstream, client: 100.80.26.1, server: unraid.<my-tailnet-domain>.ts.net, request: "GET /logterminal/compose_manager_action/ws HTTP/1.1", upstream: "http://unix:/var/tmp/compose_manager_action.sock:/ws", host: "unraid.<my-tailnet-domain>.ts.net"

Any idea why this might have started happening?

Was this after an update to anything relavent? There was an issue I had with websockets dropping due to a Chrome update enforcing HTTP/2 standards but this seems different. Please open a bug report on GitHub and I can take a closer look.

On 8/29/2026 at 11:35 AM, mstrhakr said:

Was this after an update to anything relavent? There was an issue I had with websockets dropping due to a Chrome update enforcing HTTP/2 standards but this seems different. Please open a bug report on GitHub and I can take a closer look.

Thank you, I'll add the bug report.

I'm still building my NAS and changing things each day, so it's difficult to keep track, but the thing it comes to mind is I recently updated Unraid OS from 7.3.1 to 7.3.2

I updated to v2026.08.31 and now I'm getting this on the home page. I tried toggling the features off/on, but I admit I didn't try remove/reinstall yet.

Sep 1 11:15:01 plugin-manager: executing inline script: /bin/bash '/tmp/inline1-compose.manager.sh'

Sep 1 11:15:01 plugin-manager: creating: /boot/config/plugins/compose.manager/compose.manager-2026.08.31-noarch-2148.txz - downloading from URL https://github.com/mstrhakr/compose_plugin/releases/download/v2026.08.31/compose.manager-2026.08.31-noarch-2148.txz

Sep 1 11:15:02 plugin-manager: checking: /boot/config/plugins/compose.manager/compose.manager-2026.08.31-noarch-2148.txz - MD5

Sep 1 11:15:02 plugin-manager: running: upgradepkg --install-new /boot/config/plugins/compose.manager/compose.manager-2026.08.31-noarch-2148.txz

Sep 1 11:15:04 plugin-manager: executing inline script: /bin/bash '/tmp/inline3-compose.manager.sh'

Sep 1 11:15:04 plugin-manager: executing inline script: /bin/bash '/tmp/inline7-compose.manager.sh'

Sep 1 11:15:04 plugin-manager: executing inline script: /bin/bash '/tmp/inline9-compose.manager.sh'

Sep 1 11:15:04 plugin-manager: compose.manager.plg updated

Sep 1 11:16:01 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":211,"mode":"progressive","composeListReady":true}

Sep 1 11:28:09 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":192,"mode":"progressive","composeListReady":true}

Sep 1 11:28:41 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":203,"mode":"progressive","composeListReady":true}

Sep 1 11:29:08 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":192,"mode":"progressive","composeListReady":true}

Sep 1 11:29:47 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":201,"mode":"progressive","composeListReady":true}

Sep 1 11:31:39 compose.manager: [INFO] [composeLoadlist] compose list ready - Data: {"rows":1,"elapsedMs":202,"mode":"progressive","composeListReady":true}

Edited September 1Sep 1 by jumperalex

Same issue here

Same issue. Tried turning the features "Hide Compose Containers from Docker Page" and "Hide Compose Containers from Docker Dashboard Tile" off and on again -without any result.

My beautiful UI showing all my apps is ruined - help! 😜

I am still running the version 2026.07.02. This thread gives my update anxiety.

I have a problem in my list of stacks there is one line that only says "Failed to load <name of an old stack I removed>".

I checked under /boot/config/plugins/compose.manager/projects there is one folder with the name of the old stack and it only contains one file "name" which contains the name of my old stack.

Is it safe to delete that folder to remove the error message showing in the UI?

14 hours ago, googleg said:

I have a problem in my list of stacks there is one line that only says "Failed to load <name of an old stack I removed>".

I checked under /boot/config/plugins/compose.manager/projects there is one folder with the name of the old stack and it only contains one file "name" which contains the name of my old stack.

Is it safe to delete that folder to remove the error message showing in the UI?

Yes, it populates the list by scanning the projects folder. Deleting the old one is perfectly safe.

On 9/2/2026 at 2:54 PM, menkromsen said:

Same issue. Tried turning the features "Hide Compose Containers from Docker Page" and "Hide Compose Containers from Docker Dashboard Tile" off and on again -without any result.

My beautiful UI showing all my apps is ruined - help! 😜

Updates 9/3 and took care of these issues.

On 9/3/2026 at 7:01 AM, googleg said:

I am still running the version 2026.07.02. This thread gives my update anxiety.

To be honest, I wish this was versioned like a normal program. Just forcing an update to latest with out much choice and no way to roll back is not fun for me or the users. Hopefully they rethink this as part of the rebuild they are doing for Unraid 8.