If you are able, please report issues or feature requests via GitHub; support will still be provided here but GitHub is the preferred method. https://github.com/mstrhakr/compose_plugin

Compose Manager Plus

Compose Manager installs the Docker Compose CLI plugin on your unRAID server and provides a comprehensive web-based interface to create, run, update, back up, and restore Compose stacks directly from the unRAID dashboard. It includes per-stack autostart, scheduled automatic image updates, a rich context menu mirroring the native Docker tab experience, an integrated terminal for live command output, background command execution with notifications, optional UI integration to hide Compose-managed containers, and tooling for testing and CI.

Screenshots

Main Compose Manager Interface

Compose Page

Dashboard Integration

Stack Editor

The built-in editor provides multiple tabs for managing your compose stack:

Compose Tab

Env Tab

WebUI Labels Tab

Settings Tab

Theme Support

Settings

Settings - Main

Settings - Updates

Settings - Backups

Settings - Log Viewer

Features

• Docker Compose Integration - Installs the Docker Compose CLI plugin (v5 by default) and manages stacks on your unRAID server.

• Web UI Management - Create, edit, and manage Compose stacks directly from the unRAID dashboard.

• Stack Operations - Start, stop, restart, update, pull/build, and remove stacks with one click (supports profiles and override files).

• Context Menu - Rich context menu on every stack icon with state-aware actions (see Context Menu below).

• Container Context Menu - Right-click individual containers to open a WebUI, console, or logs; start, stop, pause, resume, or restart individual containers without touching the whole stack.

• Auto-Updates - Per-stack scheduled image update checks using SHA-256 digest comparison, with a configurable scheduler, bulk "Run Now", and toggle-all controls.

• Image Pinning - Images referenced with a @sha256: digest are automatically detected as pinned and will not trigger update alerts.

• Background Execution - Any stack action (up, down, update, pull, etc.) can be dispatched in the background; a notification is shown on completion and the UI polls for when the lock is released.

• Expandable Stack Details - Click a stack row to expand an inline Docker-tab-style container table showing update status, image source/tag, network, IP, and port mapping for each container.

• Autostart & Shutdown - Configurable per-stack autostart with optional force-recreate, wait-for-Docker, and configurable timeouts. Graceful shutdown handling.

• Visibility & Filtering - Optionally hide Compose-managed containers from the native Docker UI and Dashboard tile to avoid duplicate entries (behavior varies by unRAID version).

• Backup & Restore - Manual and scheduled backups with selective restore from the UI.

• Web Terminal - Integrated ttyd terminal for live, colorized compose command output; also supports a basic output mode.

• Profiles - Full support for Docker Compose profiles, including multi-profile selection per action.

• External Paths - Compose files and env files can live outside the default projects folder (external compose path and env path per stack).

• Override File Management - Centralized management of compose.override.yaml files, including service rename handling.

• Stack Editor - Full-screen modal editor with four tabs: Compose (YAML with live validation), ENV, Web UI Labels (icon/WebUI/shell per service via override file), and Settings (name, description, icon URL, WebUI URL, default profile, external paths). Ctrl+S to save, Esc to close.

• Basic / Advanced View Toggle - Toggle between a compact view and an advanced view exposing additional columns (SHA diffs, force-update links) — scoped to the Compose tab to avoid affecting the Docker tab.

• Compose File Discovery - Automatically detects all four standard compose file names (compose.yaml, docker-compose.yaml, compose.yml, docker-compose.yml).

• Build Stack Support - Stacks with a build: section in the compose file are detected automatically; context menu and update labels adapt ("Build", "Build & Up", "Update & Rebuild").

• Indirect Stack Support - Register a stack pointing to a compose file stored anywhere on the array (outside the projects folder) using an "Indirect Path".

• Security Hardening - Path traversal prevention, shell injection hardening with safe argument arrays, XSS escaping throughout, and strict input validation.

• Developer & Testing Tools - Unit tests (PHPUnit), integration tests (BATS), static analysis (PHPStan), and CI workflows.

Installation

Community Applications

Install via the Community Applications plugin in unRAID by going to the 'Apps' tab and searching for 'Compose Manager Plus'.

Once there you will see both the main release and the beta release available to be installed. See below if you have Compose Manager already.

Manual Install

Install manually by navigating to:

Plugins → Install Plugin and entering the plugin URL:

Main Release:

https://raw.githubusercontent.com/mstrhakr/compose_plugin/main/compose.manager.plg

Beta Release:

https://raw.githubusercontent.com/mstrhakr/compose_plugin/dev/compose.manager.plg

Migration from dcflachs Docker Compose Manager (Depreciated)

When migrating from the original Compose Manager plugin, you can simply press reinstall on Compose Manager Plus to remove the old plugin and install the new one. The plugins both have the same name internally and cannot be installed at the same time. Compose Manager Plus also uses the exact same project folder structure so it will detect all your existing stacks automatically.

Safe migration path

This is usually overkill, but better safe than sorry.

• Compose down for all stacks

• Backup project directory

• Uninstall old plugin

• Install new plugin

• Start up stacks

Standard migration path

The standard way in upgrade.

• Go to App Tab (Community Applications/CA)

• Search for 'Compose Manager Plus'

• Press (re)install in Community Applications.

NOTE: I have tested upgrading in place by clicking "reinstall" in the CA app store without stopping the stacks and have has no issues personally. The only time this could be an issue is if your project is running with a project name that is different from the sanitized version of your folder name. Thats why it is safest to stop/down all stacks before migration.

Remove Compose Manager Plus and Re-Install dcflachs Docker Compose Manager

With dcflachs Docker Compose Manager being depreciated, if you want to go back to it you will need to do the following:

Disable 'Hide Depreciated Applications' in CA

• Go to Apps tab (Community Applications/CA)

• Go to Settings in the bottom of the left sidebar

• Set Hide Deprecated Applications to No.

Remove 'Compose Manager Plus' and reinstall 'Docker Compose Manager'

• Go to Apps tab (Community Applications/CA)

• Search for Compose Manager at the top.

• Find currently installed version and press Actions->Uninstall to uninstall.

• Find Docker Compose Manager and press Actions->(Re)Install to install.

Requirements

• unRAID 6.9.0 or later

NOTE: This is untested on anything older than 7.2.3 currently. I will remove this note if I get a report that this IS compatible that far back. I am working on getting a machine setup for testing on the older versions. Any advice would be welcome, eg how to VM unraid easily.

• Docker service enabled

ORIGINAL MESSAGE BELOW:

Hey everyone, I forked the original Compose Manager and upgraded it with a much nicer editor, an improved WebUI, and several UX improvements. It adds things like an improved Compose tab with expandable stacks, log viewing, and import/export of stack definitions. For now its available here: https://github.com/mstrhakr/compose_plugin

I'm working on getting it added to the app store, this post is actually the first step to that end.

Feedback is always welcome - report bugs or request features here: https://github.com/mstrhakr/compose_plugin/issues

Edited April 21Apr 21 by mstrhakr
Update to match project README.md

I now have a beta version available which will be where you can go for the bleeding edge updates. This was done because I am not the only user anymore and reliability is important, doing it this way means i can test the beta (and so can you) before pushing the changes to main for a stable release. The current beta has some back end changes that should help with maintainability but will need tested. There are also two new features in the current beta; Auto Updates and Background Command support. Please try it out and let me know how you like it. If there are any issues please make a new issue on GitHub.

Small note: This is still NOT available on the CA App Store, I have submitted the form and even reached out to Squid with no luck so far. I will update these posts with more information when I get it.

Thank you @mstrhakr I'll have to give the beta a test a drive later today.

Do we use the dev branch to test the beta version? https://raw.githubusercontent.com/mstrhakr/compose_plugin/refs/heads/dev/compose.manager.plg

17 minutes ago, Cino said:

Thank you @mstrhakr I'll have to give the beta a test a drive later today.

Do we use the dev branch to test the beta version? https://raw.githubusercontent.com/mstrhakr/compose_plugin/refs/heads/dev/compose.manager.plg

YES! There are also beta (tagged with pre-release) releases in the GitHub releases section. Latest is here https://github.com/mstrhakr/compose_plugin/releases/tag/v2026.03.11-dev.1235.

The link on the release to paste into the Install Plugin page in Unraid is https://raw.githubusercontent.com/mstrhakr/compose_plugin/dev/compose.manager.plg but from what I can tell your link will also work for installing.

On 3/11/2026 at 12:55 PM, mstrhakr said:

Small note: This is still NOT available on the CA App Store, I have submitted the form and even reached out to Squid with no luck so far. I will update these posts with more information when I get it.

I'll check it out. System shows that I added it / completed the task on March 2nd.

Quick update; This is still not available on the app store. I haven't received any feedback as to a reason so I'm assuming I've slipped through the cracks.

Its possible (although it has not been said) that having this overlap/overwrite the old Compose Manager is not allowed and having a duplicate plugin name (compose.manager) is the problem. This is intentional so I hope that not the case, this allows us to use the same project folder and keep all your existing stacks. In fact I've done some testing and you can install directly overtop the old plugin without removing it first (although I will still recommend removing it just to be safe). This has obviously only been tested with a manual install of the plugin via the GitHub link but I imagine it will be a similar process when coming from the app store.

If I learn more or hear from the admins I will update here. Thanks for being patient.

48 minutes ago, mstrhakr said:

Quick update; This is still not available on the app store. I haven't received any feedback as to a reason so I'm assuming I've slipped through the cracks.

Its possible (although it has not been said) that having this overlap/overwrite the old Compose Manager is not allowed and having a duplicate plugin name (compose.manager) is the problem. This is intentional so I hope that not the case, this allows us to use the same project folder and keep all your existing stacks. In fact I've done some testing and you can install directly overtop the old plugin without removing it first (although I will still recommend removing it just to be safe). This has obviously only been tested with a manual install of the plugin via the GitHub link but I imagine it will be a similar process when coming from the app store.

If I learn more or hear from the admins I will update here. Thanks for being patient.

I have no idea if the naming conflict is an issue or not, but if it would help move things along I would like to offer the 2 following pieces of info. As the author of the original compose.manager plugin, I intend to deprecate my plugin as so as this hits the app store as an alternative.

Additionally @mstrhakr if it turns out the name conflict is an issue and you decide to change your plugin naming, it should be fairly straight forward to write a simple project folder migration script into the .plg file. I could assist with that if it is likely to make a difference.

6 minutes ago, primeval_god said:

I have no idea if the naming conflict is an issue or not, but if it would help move things along I would like to offer the 2 following pieces of info. As the author of the original compose.manager plugin, I intend to deprecate my plugin as so as this hits the app store as an alternative.

Additionally @mstrhakr if it turns out the name conflict is an issue and you decide to change your plugin naming, it should be fairly straight forward to write a simple project folder migration script into the .plg file. I could assist with that if it is likely to make a difference.

Thanks @primeval_god I can do a copy only migration pretty easily, but I'd rather keep this plugin as a replacement instead of another option if that makes sense. I don't see any way to prevent install if Compose Manager is installed already, so keeping the name actually works in my favor. It just depends (IMO) on how CA handles this, if having a different author is enough to allow using the same name.

If it turns out I MUST rename the plugin internally I will, and like you said it shouldn't be terrible to implement a migration/copy for projects from the old one.

Also while you are here, thanks for making Compose Manager in the first place. I used it for years before I ever got the idea to upgrade it.

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

not sure if it's just me, but using the beta version from CA, I don't see any compose option (I enabled in header), in either the header or the docker tab.

EDIT: ignore me, I didn't see the apply button all the way on the bottom of the plugin screen. All is working

Edited March 25Mar 25 by erdius
edit

2 hours ago, erdius said:

not sure if it's just me, but using the beta version from CA, I don't see any compose option (I enabled in header), in either the header or the docker tab.

EDIT: ignore me, I didn't see the apply button all the way on the bottom of the plugin screen. All is working

I will NOT ignore you! lol but i wonder if I can have it float at the bottom instead of having to scroll all the way down. I'll investigate.

I currently use the https://forums.unraid.net/topic/114415-plugin-docker-compose-manager/ plugin, is it quite easy to migrate across or is there steps involved in doing so?

So this is interesting and the behavior may change in the future, but currently when you look up Compose Manager Plus in the CA app store when you already have Compose Manager installed you will get the option to reinstall instead of install. This plugin will slot in directly in place of the original. I kept the underlying name the same to prevent them from both being installed and to allow for the projects to be available to the Plus version by default.

In short, you find it on the store and click reinstall and you are all set.

There are many more options though so check out the settings page.

Oh and be sure to try the beta if you want to try the bleeding edge.

Can you add options to configure the statup order of the stacks and delays between them?

How is the migration from the old docker compose manager? Do i have to unistall it first?

What about auto updates? Any plan for this?

Edited March 26Mar 26 by L0rdRaiden

2 hours ago, L0rdRaiden said:

Can you add options to configure the statup order of the stacks and delays between them?

How is the migration from the old docker compose manager? Do i have to unistall it first?

What about auto updates? Any plan for this?

I just migrated to Compose-Manager-Plus. I stopped my containers, backed up my stacks, swapped the plugins, and restarted. Everything is working flawlessly!

Edited March 26Mar 26 by Sascha147

This plugin appears to conflict with FolderView Plus, causing the container list to malfunction on the Docker management page.

6 hours ago, AceSpace said:

This plugin appears to conflict with FolderView Plus, causing the container list to malfunction on the Docker management page.

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.

11 hours ago, L0rdRaiden said:

Can you add options to configure the statup order of the stacks and delays between them?

How is the migration from the old docker compose manager? Do i have to unistall it first?

What about auto updates? Any plan for this?

Check out the beta, it has auto updates, background actions and many bug fixes. Although if everything goes well I'll be merging it tomorrow.

I've noticed that the Advanced View only changes the compose side of things, i've lost all advanced metrics in relation to my containers.

Could someone confirm the upgrade procedure, how to safely move from the deprecated plugin to Compose Manager Plus?

Thank you.

50 minutes ago, googleg said:

Could someone confirm the upgrade procedure, how to safely move from the deprecated plugin to Compose Manager Plus?

Thank you.

Stop all your stacks, uninstall the old one, install the new one, start your stacks back up. That's all there is to it.

Edited March 26Mar 26 by primeval_god

Ok thanks. But when you say "stop your stack" do you mean compose down or stop the containers individually?

Edited March 26Mar 26 by googleg

25 minutes ago, googleg said:

Ok thanks. But when you say "stop your stack" do you mean compose down or stop the containers individually?

Safest will always be:

• Compose down on everything.

• Back up all the compose files and env files.

• Uninstall current plugin

• Install new plugin

With that said, I have done in place upgrades from the original the the new one with no issues. Going down for all is still safest though.

is this compatible with the folder view 3 plugin chagnes?

or should i uninstall both the compose manger and folder view 3 before attempting this plugin?

https://forums.unraid.net/topic/197223-plugin-folderview3/