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)