Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] Compose Manager Plus

Featured Replies

21 hours ago, mstrhakr said:

It's possible this is a bug in docker manager, the fix is in Unraid 7.3. I had a similar issue with a WordPress container and this pull request below is what fixed it.

https://github.com/unraid/webgui/pull/2581

I'm already on 7.3 RC 1 and it seems to still happen. I wonder if it is an issue specific to monica, how can i check if it is already the latest version or not?

  • Replies 187
  • Views 21.9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Kilrah
    Kilrah

    For the record I had a similar issue and had to do some cleanup

  • mstrhakr
    mstrhakr

    Great news! Compose Manager Plus is now listed in the CA App Store. Both the release version and the beta track. @primeval_god FYI

  • mstrhakr
    mstrhakr

    This should be fixed in the beta already if you'd like to take a look. I should be merging dev into main tomorrow if I can finish fixing the CSS. I hate CSS.

Posted Images

Could this somehow be related to the fact I'm running two versions of the same container (one for cron)? When i check the docker digests, I see that one of the SHA256 terms matches the latest version while one doesn't

monica                                       latest        sha256:23174c71b2d245588572859d470629ad282db565d78692310042b9261cb97ac4   583089e9e94f   6 days ago      691MB
monica                                       latest        sha256:7d55a04bce4e56da3fa047d23bd2e616cba6327bdca8147ed7255f4dc03e6cdf   583089e9e94f   6 days ago      691MB
  • Author
2 hours ago, rama3124 said:

Could this somehow be related to the fact I'm running two versions of the same container (one for cron)? When i check the docker digests, I see that one of the SHA256 terms matches the latest version while one doesn't

monica                                       latest        sha256:23174c71b2d245588572859d470629ad282db565d78692310042b9261cb97ac4   583089e9e94f   6 days ago      691MB
monica                                       latest        sha256:7d55a04bce4e56da3fa047d23bd2e616cba6327bdca8147ed7255f4dc03e6cdf   583089e9e94f   6 days ago      691MB

The two versions of the same container should be on the same sha, but it looks like one is behind. Are both of these instances in Compose Manager?

32 minutes ago, mstrhakr said:

The two versions of the same container should be on the same sha, but it looks like one is behind. Are both of these instances in Compose Manager?

Yes they are run with the same docker compose file:

services:
  monica:
    image: monica
    container_name: monica
    env_file: .env
    ports:
      - 880:80
    volumes:
    # CHANGE YOUR PATH HERE
      - /mnt/user/appdata/monica:/var/www/html/storage
    labels:
      - traefik.enable=true
      - traefik.http.routers.monica.entryPoints=https
      - traefik.http.routers.monica.middlewares=securityHeaders@file
      - traefik.http.routers.monica.rule=Host(`monica.mydomain.com`)
    restart: always
    networks:
      - custom

  cron:
    image: monica
    container_name: monica-cron
    env_file: .env
    restart: always
    volumes:
    # CHANGE YOUR PATH HERE
      - /mnt/user/appdata/monica:/var/www/html/storage
    command: cron.sh
    networks:
      - custom

networks:
  custom:
    driver: bridge
    name: custom
    external: true
1 hour ago, rama3124 said:

Yes they are run with the same docker compose file:

You should typically not have multiple containers with the same name...

  • Author
36 minutes ago, Kilrah said:

You should typically not have multiple containers with the same name...

In his compose file the container_name and service name were both unique. Same image, but different container and service names. Not sure how only one could possibly be out of date.

services:
  monica:
    image: monica
    container_name: monica
...

  cron:
    image: monica
    container_name: monica-cron
...

Is there a way to manually force the other one to update via CLI? I'm not that familiar with docker compose commands since I usually just rely on unraid app store

Edited by rama3124

  • Author

Have you done a compose down, then up?

21 minutes ago, rama3124 said:

Is there a way to manually force the other one to update via CLI? I'm not that familiar with docker compose commands since I usually just rely on unraid app store

  • 2 weeks later...

Hello. Great plugin, thanks for making this. I just have a question.

Is it possible to make the stack/s stop at the 'last' position? While there are containers that the stack/s are dependent on, they are also the ones that should be stopped first before the dependencies.

  • Author

This plugin just does Compose Down so it's only doing what compose would normally do.

I am on unRaid 7.3 (it might be relevant) but I am not seeing an option to delete the stack. I can see update/compose up and down etc. but not delete.

Its not a big issue but thought I might mention it.

  • Author
58 minutes ago, Dimtar said:

I am on unRaid 7.3 (it might be relevant) but I am not seeing an option to delete the stack. I can see update/compose up and down etc. but not delete.

Its not a big issue but thought I might mention it.

First i would do a hard refresh in your browser. `[CTRL]+[SHIFT]+[R]`

I'll look into this and see how this could happen. Doesn't seem possible at first glance of the code.

Looks like a layout problem, it's there but somehow ends up under the bottom bar

image.png

Opening the menu extends the page but not enough for all of it to fit.

Edited by Kilrah

  • Author
1 minute ago, Kilrah said:

Looks like a layout problem, it's there but somehow ends up under the bottom bar

image.png

Oh hey, thanks Kilrah, this should be easily fixable.

Is this compatible with 7.2.6? I'm having a lot of problems after updating from 7.2.4

  • Author
34 minutes ago, Tetricz said:

Is this compatible with 7.2.6? I'm having a lot of problems after updating from 7.2.4

There was a major docker upgrade that comes with some changes. I have not tested this but it should work, 7.2.5 is the furthest I've had time to update to at this time though. I have had no issues there which includes the docker upgrades. What kind of problems are you having?

Edited by mstrhakr
Issues -> changes

For some reason the count for the amount of containers is all over the place. Some stacks are more and one has 0/1 when it should have 2.

This is from fresh. Everything was removed/reset prior to hitting compose up.

  • For my jellyfin stack.

✘ Container 5877e52c388e Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /mnt/cache/appdata/jf-cache

There is no volume that contains that path in the docker compose.

services:
  jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    volumes:
      - /mnt/cache/appdata/jellyfin:/config
      - /dev/shm/jellyfin:/transcodes
      - /mnt/user/media:/media:ro
    ports:
      - 8096:8096/tcp
    restart: unless-stopped
    devices:
      - /dev/dri:/dev/dri
  • For my Immich stack, it says

[+] up 76/78
Image ghcr.io/immich-app/immich-server:release Pulled 35.3s
Image docker.io/valkey/valkey:9@sha256:3b55f... Pulled 6.5s
Image ghcr.io/immich-app/postgres:16-vectorc... Pulled 1.2s
Image ghcr.io/immich-app/immich-machine-lear... Pulled 26.6s
Network immich_immich Created 0.0s
Network immich_internal_immich Created 0.0s
⠹ Container ce6bf163fb3b Recreate 0.2s
✘ Container aea52a9b7861 Error response from daemon: No such container: aea52a9b7861f60cf1f56ccf99e695efca66bda16062f21344bf66be78a6ffa0 0.2s
Container 9e9a4a0540eb Removed 0.0s
⠹ Container b4ef314f79f9 Recreate 0.2s
Error response from daemon: No such container: aea52a9b7861f60cf1f56ccf99e695efca66bda16062f21344bf66be78a6ffa0

✗ Stack immich failed to start (exit code: 1)

Let me know if I can provide any other information.

Edited by Tetricz

Upon further investigation, there are a bunch of "containers" which are non existent showing up.

Found the problem was most likely another plugin. The RAMDisk for docker logs plugin. I removed it rebooted and everything started working again. Hopefully if anyone runs into this problem, they'll find my posts

5 hours ago, Tetricz said:

Found the problem was most likely another plugin. The RAMDisk for docker logs plugin. I removed it rebooted and everything started working again. Hopefully if anyone runs into this problem, they'll find my posts

For the record I had a similar issue and had to do some cleanup

  • 2 weeks later...

Has anyone noticed that the comfigured stacks are NOT auto starting when docker is done settling? All my stacks are set to do so. I see no attempt in the logs to bring them up.

Aside...I had to remove 'unraid-autostart' in /var/lib/docker as a nice legacy from dockerman. I am really trying to neuter dockerman in lieu of compose. I really hope, like others, we end up a docker solution for simple setups AND a purely compose setup for advanced users. Limetech....this shouldn't be hard to implement with a switch :-)

TY.

Kev.

...I do see the beta branch is addressing this...let's wait and see...

I'm seeing the same problem TDD - stacks with more than one container in them fail to start.

Deleting stacks is also pretty broken - the UI says (Stop first) but it doesn't. You need to stop it then delete and MAYBE it deletes it in 1-2 tries.

Switching to using Compose has made me think that perhaps a VM running Portainer is the better way to go for anyone who finds the Unraid App setup restricting. Compose on Unraid just doesn't seem super reliable and the fact that the original plugin is gone makes me wonder if I'll be looking for CMP's replacement in 2-3 years.

Edited by rampantandroid

I am really looking to neuter dockerman. I actually just use the plugin (TY BTW!) for controlled autostarts of my stacks. Futher management of everything falls to Dockhand. Dockhand is the only container that dockerman starts. All stacks are placed on my /appdata in a folder when both the plugin and Dockhand can see them, so there is no contention or compose files out of sync.

Just this startup thing...

End of the day it is not a big stretch to make Dockhand the orchestrator. I believe the next version of it will support autostart compose.

Kev.

On 5/11/2026 at 7:54 PM, Tetricz said:

For some reason the count for the amount of containers is all over the place. Some stacks are more and one has 0/1 when it should have 2.

This is from fresh. Everything was removed/reset prior to hitting compose up.

  • For my jellyfin stack.

✘ Container 5877e52c388e Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /mnt/cache/appdata/jf-cache

There is no volume that contains that path in the docker compose.

services:jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    volumes:
      - /mnt/cache/appdata/jellyfin:/config
      - /dev/shm/jellyfin:/transcodes
      - /mnt/user/media:/media:ro
    ports:
      - 8096:8096/tcp
    restart: unless-stopped
    devices:
      - /dev/dri:/dev/dri
  • For my Immich stack, it says

[+] up 76/78
Image ghcr.io/immich-app/immich-server:release Pulled 35.3s
Image docker.io/valkey/valkey:9@sha256:3b55f... Pulled 6.5s
Image ghcr.io/immich-app/postgres:16-vectorc... Pulled 1.2s
Image ghcr.io/immich-app/immich-machine-lear... Pulled 26.6s
Network immich_immich Created 0.0s
Network immich_internal_immich Created 0.0s
⠹ Container ce6bf163fb3b Recreate 0.2s
✘ Container aea52a9b7861 Error response from daemon: No such container: aea52a9b7861f60cf1f56ccf99e695efca66bda16062f21344bf66be78a6ffa0 0.2s
Container 9e9a4a0540eb Removed 0.0s
⠹ Container b4ef314f79f9 Recreate 0.2s
Error response from daemon: No such container: aea52a9b7861f60cf1f56ccf99e695efca66bda16062f21344bf66be78a6ffa0

✗ Stack immich failed to start (exit code: 1)

Let me know if I can provide any other information.

most likely a issues with the compose file database. have not had issues with the RAM disk plugin. so i can only assume based on the error reported.

https://github.com/bmartino1/unraid-docker-templates/blob/main/Guides/Compose/Immich/ImmichReadme.md

https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html

The database needs a env line for pgdata and mapped to the same mount point due to changes and upgrades...

My bet without seeing the compose is you are using the older Bitnami Redis that was removed from the Docker Hub.

so the compose is calling a Docker that no longer exists.

Edited by bmartino1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.