FolderView3 is to continue support for FolderView2 by @VladoPortos in an effort to keep the original plugin FolderView by @scolcipitato, alive.

FolderView3 lets you create folders for grouping Dockers and VMs together to help with organization.

 

Getting Started: A new button named "Add Folder" will appear at the bottom of the docker and VM tab(s) next to "Add Container".

LINKS

GitHub - folder.view3

XML

Screenshots

 

COMPATIBILITY

Compatible with Unraid 7.0+. On Unraid 7.2+, the plugin automatically uses the GraphQL API and WebSocket stats for lower latency — no configuration needed. All features fall back gracefully on older versions.

AUTOSTART

This has been improved upon from the previous versions.

• Containers marked for autostart will now autostart as they appear on the Docker page

  You can confirm this with cat /var/lib/docker/unraid-autostart in the Unraid console

VM SUPPORT

FolderView3 supports folder organisation for VMs, allowing you to group and manage your virtual machines the same way as Docker containers.

DASHBOARD OPTIONS

FolderView3 allows you to customise how containers and VM's appear on your dashboard, see the styling options here.

MIGRATING FROM FolderView OR FolderView2

1. In your old plugin, go to Plugins → FolderView and click Export All for both Docker and VM folders

2. Backup your custom CSS if you're using them in the styles folder config\plugins\folder.view\styles

3. Uninstall the old plugin

4. Install FolderView3 using the URL below

5. Go to Plugins → FolderView3 and Import your exported files

6. Copy your custom CSS files back into the styles folder

7. If there are visual errors on the docker, VM or dashboard pages please try deleting your cache/browser history before reporting a bug.

BUG/ISSUE REPORTS

Please if you notice a bug there’s a few things you can do to help me provide a quick fix.

1. Open dev console (F12) on the page where you notice the bug and check for any errors and note them.

2. Open your syslog and check for errors and note them.

3. Attempt a hard refresh and cache clear and see if this resolves your issue, if this doesn’t resolve your issue and the errors in your logs and console persist please submit a BUG/ISSUE report here or on GitHub with the following information.

   • Note any other plugin and plugin version that also modifies the page you are viewing.

   • Mention your Unraid version and FolderView3 version in your bug report.

   • Capture debug information mentioned below or as per the github issues report.

 

DEBUG MODE

To enable debug mode, type fv3debug on any FolderView3 page (Docker, VM, or Dashboard). You should see a console message confirming it's enabled. Debug output appears in the browser console (F12) with a [FV3] prefix. State persists across page loads — type fv3debug again to disable.

For PHP server-side debug: run touch /tmp/fv3_debug_enabled on the Unraid console. Logs write to /tmp/folder_view3_php_debug.log.

If you have a problem you will likely be asked to share the console output.

 

CUSTOM CSS/SCRIPT

Using custom CSS/scripts is easy, just download the files and import it with the button in the settings.

COMMUNITY CSS

• hernandito — Compact and Midsize designs

• masterwishx — urblack with CSS variables

• Mattaton — urblack, urgray, urwhite themes

All three can be imported directly from the CSS Tool on the settings page.

FolderView3 has a built-in CSS Tool on the settings page (Settings → FolderView3) with four tabs:

• Themes — import community CSS directly from GitHub by pasting a repo URL. Themes show update status with one-click updates.

• Variables — edit 27+ CSS variables with color pickers and sliders

• Presets — one-click theme presets

• Advanced CSS — free-form CSS editor

You can still manually place CSS/JS files in the config/plugins/folder.view3/styles/ and scripts/ folders if you prefer.

 

For the ones brave enough to make custom CSS or scripts, on GitHub you will find a README with all the instructions.

Please note that if you are coming from earlier installations of FolderView your custom CSS may not be directly compatible. Please review the above readme before migrating.

 

TRANSLATIONS

If you want to translate this plugin, you can find the files here, but before read below.

The "locale" field and the name of the file should be an ISO 639-1 language code.

If you translate, don't edit any HTML tags you see, only edit text.

In the translation file, you might encounter the symbol $ followed by a number, you can't remove them, but you can move them around as much as you want.

 

DOCKER LABELS

Add the label folder.view3 with the folder name as the value to any container or Docker Compose service:

• Create the folder first and then add the label to your compose.

services:
  myapp:
    labels:
      folder.view3: "MyFolder"

 

FAQ

BEFORE asking, please search if any other user asked the same thing, you might find your solution.

Q: How can I sort the content of a folder?
A: In the edit folder page, you can drag and drop the containers/VM just like the normal docker page.

Q: How can I sort the folder themselves?
A: In the docker page since 6.12 there is a padlock green icon in the toolbar, click that, and you can just drag and drop the folder like normal containers/VM.

Q: Where can I report a bug?

A: Either here or on my GitHub issues, please check and make sure it hasn’t already been reported. But if you have further information on an existing bug report please feel free to comment.

Q: I updated and my docker or VM page don’t look right, what do I do?

A: Press F12 and check the developer console for errors, check unraid syslog for errors as well. If neither of those show anything obvious follow the debug instructions above and report them here so I can identify the issue and resolve it.

 

FolderView3 Plugin Update History

###2026.05.15

- Fix Reset Order button (was silently broken by FV3's request interceptor)

- Folders now sort alphabetically when no manual order is set

- VM tab Reset Order also fixed

###2026.05.07

- Fix folder editor failing to load when a container has no Docker labels

###2026.05.02

- Uptime column now only appears as required

- Other various fixes/cleanup from this implementation

###2026.04.30

- Docker table column lock and layout stability fixes

- Folder-name pill and chevron polish (Firefox border fix, CSS preset alignment, fluid resize)

- Advanced popup and dashboard toggle consistency

- Folder RAM total now respects per-container --memory= limits

- Richer debug JSON export for diagnostics

- Misc bug fixes and cross-plugin robustness

###2026.04.17

- Minor 7.0.x compatibility fix

###2026.04.14

- Unraid 7.0.x compatibility fixes

- Mobile advanced preview and tooltip improvements

- Atomic file writes and safer JSON handling

- Extend incognito mode to advanced preview tooltips

- CSS cleanup and layout fixes

- UI polish and bug fixes

###2026.04.09

- Harden incognito mode: scrub volume paths, image tags, and registry prefixes in expanded rows

###2026.04.08

- Fix preview clipping hiding containers due to sub-pixel rounding with custom CSS themes

- Fix row separator false row breaks from sub-pixel rounding

- Fix dashboard fullwidth panel row detection tolerance

- Compute VM name column width from actual icon and padding sizes

- Fix VM name column width selector (was targeting non-existent element)

- Fix incognito mode not hiding container registry/image info in "By:" fields

- Fix incognito auto-apply racing with folder creation on page load

###2026.04.07

- Fix preset accent color overriding orange update-available text

###2026.04.06

- Fix folder settings page toggles showing wrong state on load

###2026.04.05

- Incognito mode: scrub volume paths, public IPv6, MACs, disk filenames, non-standard interfaces

- Incognito mode: VM previews now show "VM 1" instead of "Container 1"

###2026.04.04

- Shared code extraction and CSS consolidation for improved maintainability

- GraphQL API integration with WebSocket stats and automatic PHP fallback

- Settings page modernization with folder defaults and full backup/restore

- CSS Tool with theme manager, presets, variables, and GitHub import

- Incognito mode for screenshot-safe sharing

- Pre-install cleanup for reliable upgrades

- VM detail row positioning fixes in folders

- Mobile and touch improvements

###2026.04.01

- Sanitize debug exports

###2026.03.30.2

- Add Folder button relocated next to Add Container/VM

###2026.03.30.1

- Mobile UI improvements

###2026.03.30

- Fix preview overflow causing table expansion for users with a large number of containers in a folder

###2026.03.28

- Fix preview divider and wrapper vertical alignment

- Fix expand mode containers overlapping on page refresh

- Fix row separator timing on basic/advanced toggle

- Fix default folders wrapping on narrow screens

- Add Firefox scrollbar fallback

- Add expand row separator gap spacing

- Enhanced mobile UI

###2026.03.27

- Fix multiple JS bugs

- Fix preview divider alignment across all overflow modes

- Smart overflow detection — scroll/expand only applied when content overflows

- Theme-aware custom action dialog

- Deduplicate API requests on page load

###2026.03.24

- Row separator as configurable folder setting

- Fix containers ejected from folders after rename

- Preview borders adapt to advanced view row height

- Mobile device UI improvements

- Scroll overflow preview centering fix

###2026.03.23.3

- Fix chevron position shift when expanding/collapsing folders

###2026.03.23.2

- Dynamic folder name column width — expands/shrinks to fit folder name

###2026.03.23.1

- More custom CSS support for inset style

###2026.03.23

- Fix fullwidth panel appearing in wrong row after Started only toggle

- Fix chevron missing position styles after Started only toggle

- Fix dashboard fullwidth panel and chevron positioning after Started only toggle

- Add fv3-* CSS classes to all dashboard folder elements for custom themes

- Add fv3-standalone class for containers/VMs not in folders

- Fix dashboard alignment on narrow screens for inset, embossed, fullwidth layouts

- Fix expanded panel remnant when toggling Started only filter

- Fix chevron position after toggling Started only filter back

- Fix animation firing when disabled in dashboard settings

- Fix fullwidth panel ordering after Started only toggle

- Fix fullwidth chevron positioning to match inset layout

- Restore static chevron positioning for accordion and embossed layouts

###2026.03.21

- Add Embossed dashboard layout style

- Add expand/collapse animation option for dashboard layouts

- Add CSS custom properties for inset and embossed panel theming

###2026.03.20.2

- Inset quick collapse tweak

###2026.03.20.1

- Fix inset panel chevron positioning and SVG border sizing

###2026.03.20

- Add folder name clipping for inset layout when collapsed

- Fix fullwidth panel pushing non-folder items to wrong row

- Add fullwidth panel reflow on window resize

- Add 20 character warning for folder names to folder settings page

###2026.03.19.2

- Fix fullwidth panel placement for expanded folders on dashboard

###2026.03.19.1

- Fix dashboard settings race condition when switching layouts

###2026.03.19

- Fix folder name/icon not vertically centered on Docker and VM pages

- Reorganize dashboard settings with Docker/VM section headings

- Convert Yes/No settings to Unraid-native On/Off toggle switches

- Fix chevron button alignment on Docker and VM pages

- Add Quick collapse (expand toggle) for non-Classic dashboard layouts

- Add per-folder preview overflow setting (Default / Expand Row / Scroll)

- Add responsive mobile breakpoints for dashboard child tiles

- Auto-width dashboard tiles for folders with ≤3 children

- Dynamic NAME column width on VM page

- Inset dashboard style improved

###2026.03.16

- Fix folder editor tooltips

- Export now preserves folder order matching Docker/VM container page

- Add new CSS variables for customizable layout and colors

- Enhanced security: ID validation, JSON safety, file permissions

- Lazy-load libvirt to prevent crashes when VM manager unavailable

###2026.03.07

- Allow custom CSS to override VM row alternating colors

###2026.03.06

- Fix VM tab row alternating colors with folders

- Fix Compose Manager compatibility

###2026.03.05

- Add per-container "Hide Preview" toggle in folder editor

- Center toggle alignment in folder editor table

- Restrict drag cursor to container name content

###2026.03.04.1

- Fix cached scripts not refreshing after update

- Fix action buttons clipped on settings page on mobile

- Fix VM folder row markup

- Fix settings page button layout overflow

###2026.03.04

- Minor security improvements to align with Unraid best practices

- Fix empty folder showing "3rd Party" label

- Fix invalid regex pattern in folder name input

###2026.02.26

- Fix folder rendering crash for container names containing CSS special characters (e.g. periods, colons)

###2026.02.24

- Add Docker Compose and 3rd Party container awareness for folders

- Fix false orange update text on Compose/3rd Party containers

- Fix autostart counting and toggle for non-dockerman containers

- Show stacked Compose + 3rd Party labels for mixed folders

- Fix tooltip operator precedence bug for update status

- Fix compose container duplicate on folder settings page

- Fix folder drag-and-drop for compose/3rd-party-only folders

- Improved folder expand button shifting when folder is toggled

- Dashboard folder/container names show orange text when updates available (per folder setting)

- Sort unsorted containers alphabetically on folder settings page

###2026.02.19

- Fix container autostart with wait timer being disabled on tab switch

###2026.02.17.1

- Fix folder export triggering Unraid external link warning

###2026.02.17

- Fix VM folder collapse button not working (hardcoded colspan selector)

- Fix VM folder crash when regex is invalid

- Fix VM folder crash when a deleted VM is still in folder config

- Fix VM context menu crash during folder rebuild

- Fix VM folder action error messages showing boolean instead of text

- Use translated error title for VM folder actions

###2026.02.16.1

- Fix VM folder column alignment and autostart toggle possition

###2026.02.16

- Rebrand from FolderView2 to FolderView3

- Docker label changed from folder.view2 to folder.view3

- Fix plugin settings page table alignment

- Remove deprecated container autostart order indicator

###2026.02.15

- Fix VM folder image and name missing CSS classes on Dashboard

###2026.02.11

- Add folder WebUI setting with context menu button

- Clean stale containers from autostart on page load and folder save

###2026.02.10

- Fix autostart toggle race condition when toggling folder-level autostart

- Sync container autostart order to match folder settings layout

- Fix folders not loading after reordering containers

- Remove commented-out debug code and stale files

###2026.02.09.1

- Fix dashboard showing wrong containers in folders

###2026.02.09

- Fix folder autostart toggles showing OFF after plugin update

- Fix color reset button appearing below color swatch

- Change new folder defaults to all toggles OFF

###2026.02.08

- Fix folder name wrapping in basic view

- Backward-compatible Docker Manager theme CSS for Unraid 6

###2026.02.07

- Fix VM folder assignment bug

- Fix CPU/Memory text wrapping in advanced view

- Translation updates for de, es, it, pl, zh

###2026.02.05

- Fix archive packaging structure

###2026.02.04

- Split border and vertical bars into separate color pickers

- Border/bars color settings now nested under their toggles

- Fix expanded folder bottom border color

###2026.02.03

- Fix folder CPU and Memory stats not updating in advanced view

- Fix Docker Compose containers not grouping into folders

- Fix Advanced Preview tooltip for all Unraid themes

- Fix folder settings page layout

- Remove missing Docker Manager CSS reference

Disclaimer: This has been forked and fixed/updated with claude code - originally for personal use but it seemed like there was a need to share the fork as FolderView2 was no longer maintained. I have kept a detailed changelog of everything that has been modified when compared with the upstream repository. This can be found on my repository.

Edited May 14May 14 by chodeus

hi. migrating from folderview2 here.

when i press export on both the old and new foldervier. it doesnt download any json file instead it just comes out something like this.
do i need to re-do each folder?

thanks

1 hour ago, i1mran92 said:

hi. migrating from folderview2 here.

when i press export on both the old and new foldervier. it doesnt download any json file instead it just comes out something like this.
do i need to re-do each folder?

thanks

That is not something I have experienced.
It is safe to export all, you need your vm and docker.json files so you dont have to recreate your folders.

But if you're not comfortable with accepting this security warning you can manually download your docker.json and vm.json in your flash drive to another location and then remove the old folderview and then copy them back into the newly created files once you have installed folder.view3.

I need to figure out if it's as simple as clearing my cache for me to reattempt this Unraid security warning and then I can look at options to not trigger that security warning.

Edit: resolved the issue, there won't be any uneccessary security warnings when exporting your folders. BUT you will need to update FolderView3 for that to be resolved.

2026.02.17.1

• Fix folder export triggering Unraid external link warning

Edited February 17Feb 17 by chodeus
Posted resolution for issue.

i was able to get it working.

even after i accepted that warning, it didnt download the .json file. i tried to manually download from the plugins folder and that worked.

though i tested again, once i accepted the warning to not show anymore, it automatically download the .json file, if not it will not download the .json file

but thank you for continuing the project. its in a much better state now. no bugs i found so far. opening the webui also works where usually last time it just show an empty IP

Edited February 17Feb 17 by i1mran92

3 minutes ago, i1mran92 said:

i was able to get it working.

even after i accepted that warning, it didnt download the .json file. i tried to manually download from the plugins folder and that worked.

though i tested again, once i accepted the warning to not show anymore, it automatically download the .json file, if not it will not download the .json file

but thank you for continuing the project. its in a much better state now. no bugs i found so far. opening the webui also works where usually last time it just show an empty IP

I know if I'm using chrome sometimes I need to prevent the downloaded file from being deleted by clicking "keep" on the download attempt top right corner of my window.

Glad you got it up and running! Please report here or on my github if you do notice any bugs.
Enjoy!!

Thanks for your work on this. Do users of FolderView3 still need to manually the http://IP:Port in this version? I recall back in the day that wasn't necessary to open the WebGui but for me I must manually add the IP:Port. Just curious if I missed something and the default is working for other users. Thank you.

Fresh install. Unable to add a "wait" time to a container I've added to a folder. In fact, if I add a wait time, this actually toggles Autostart OFF for that container.

9 hours ago, BigNavy said:

Thanks for your work on this. Do users of FolderView3 still need to manually the http://IP:Port in this version? I recall back in the day that wasn't necessary to open the WebGui but for me I must manually add the IP:Port. Just curious if I missed something and the default is working for other users. Thank you.

Standard webUI settings in the template is all you need.

6 hours ago, manHands said:

Fresh install. Unable to add a "wait" time to a container I've added to a folder. In fact, if I add a wait time, this actually toggles Autostart OFF for that container.

I don’t use this unraid feature but I’ll have a look today, thankyou for letting me know!

Edited February 18Feb 18 by chodeus

7 hours ago, manHands said:

Fresh install. Unable to add a "wait" time to a container I've added to a folder. In fact, if I add a wait time, this actually toggles Autostart OFF for that container.

Awesome reporting thankyou, was an easy problem to troubleshoot and fix.

Please update.

13 hours ago, chodeus said:

Awesome reporting thankyou, was an easy problem to troubleshoot and fix.

Please update.

Looks to be working now ... thanks for the quick turnaround!

Quick update, on Monday I sorted out everything that I believe is required to have this added to the CA + submitted the form requesting this/my repository to be added so people can install via the Community Applications and we can close down FolderView2.

I anppreciate everything Vlado did to migrate FolderView to Unraid7 and keep it going.

@chodeus

This is great, thanks! Glad to see the plugin being actively maintained again.

Quick question - when you are configuring a new docker folder, the docker list is not alphabetically sorted, making it tedious to find the docker containers that you want to add to the folder. Is that fixable?

5 hours ago, msalad said:

@chodeus

This is great, thanks! Glad to see the plugin being actively maintained again.

Quick question - when you are configuring a new docker folder, the docker list is not alphabetically sorted, making it tedious to find the docker containers that you want to add to the folder. Is that fixable?

On this screen you can drag and drop these containers to any order you wish. Just note that this is also your container start order if you have autostart toggled on.

Just hover over the title and click and drag.

11 minutes ago, chodeus said:

On this screen you can drag and drop these containers to any order you wish. Just note that this is also your container start order if you have autostart toggled on.

Just hover over the title and click and drag.

Hmm that's interesting because the order of my containers on the folder page does not reflect the order of my containers on my docker page (which is also the container start order). The container order on the folder page is seemingly random for me.

I also have 70+ containers for manually rearranging them would be quite tedious. I was hoping your plugin had control over the sorting when you read/import my container list to show them on the folder page

Edited February 22Feb 22 by msalad

3 minutes ago, msalad said:

Hmm that's interesting because the order of my containers on the folder page does not reflect the order of my containers on my docker page (which is also the container start order). The container order on the folder page is seemingly random for me.

I also have 70+ containers for manually rearranging them would be quite tedious. I was hoping your plugin had control over the sorting when you read/import my container list to show them on the folder page

Are you happy to share screenshots so I can see what you are seeing?

If I move whisper to under VM custom icons, it moves.

5 minutes ago, chodeus said:

Are you happy to share screenshots so I can see what you are seeing?

If I move whisper to under VM custom icons, it moves.

Ok I see, we are talking about two different things. Yes you're right, for dockers that have been added to a folder, if I then edit that folder I can drag and drop to rearrange them and that works as you describe.

I'm talking about when you are creating a new docker folder and selecting which dockers you want to be in that folder. The full list of docker containers that is shown is displayed in a seemingly random order. For example, on my Docker page my first few containers are these

But when I create a new docker folder and go to select which dockers I want to include in that folder, the first few dockers listed are these

9 minutes ago, msalad said:

Ok I see, we are talking about two different things. Yes you're right, for dockers that have been added to a folder, if I then edit that folder I can drag and drop to rearrange them and that works as you describe.

I'm talking about when you are creating a new docker folder and selecting which dockers you want to be in that folder. The full list of docker containers that is shown is displayed in a seemingly random order. For example, on my Docker page my first few containers are these

But when I create a new docker folder and go to select which dockers I want to include in that folder, the first few dockers listed are these

Oh I see!

I’ve never thought to query the order of that list because it’s just how it always was with the original FolderView and then FolderView2. I’ll have a look into it and see what the impact is of making the list of “unsorted” containers appear in alphabetical order, I can’t see an issue though.

Thankyou for the fresh eyes and the suggestion!

48 minutes ago, chodeus said:

Oh I see!

I’ve never thought to query the order of that list because it’s just how it always was with the original FolderView and then FolderView2. I’ll have a look into it and see what the impact is of making the list of “unsorted” containers appear in alphabetical order, I can’t see an issue though.

Thankyou for the fresh eyes and the suggestion!

Thanks for taking a look!

Hey Mate. Cool to see the plugin being developed again.

Just here asking two things though.

First, you mentioned you co-authored using Claude, could you elaborate a bit more what that means in your case? Did you write any code, or did you just approve claude's code? Do you know and can write the programming languages that folder.view(2) is written in? Looking at you GitHub repo it doesn't look like you have much experience in programming at all? How can one make sure you will continue developing this tool?

Second, nonetheless to my questions from First I would still like to mention here that I have an open PR over at the folder.view2 repo https://github.com/VladoPortos/folder.view2/pull/21 that I would like to see merged. You mentioned you didn't change that much (although 104 commits indicate otherwise), so it should be pretty easy to bring my changes over to this repo (you should be able to bring over my changes to your repo, without me having to open a pr at your repo).

Of course this would only matter if you really want to continue supporting this plugin in the long-term (it's annoying that we already need a v3 here) and if you are even interested in the changes I did in my PR.

12 hours ago, msalad said:

Thanks for taking a look!

This was simple, it will be in the next stable release.

Unsorted containers will appear in alphabetical order on the folder settings page.

Thankyou for the suggestion!

11 hours ago, Joly0 said:

Hey Mate. Cool to see the plugin being developed again.

Just here asking two things though.

First, you mentioned you co-authored using Claude, could you elaborate a bit more what that means in your case? Did you write any code, or did you just approve claude's code? Do you know and can write the programming languages that folder.view(2) is written in? Looking at you GitHub repo it doesn't look like you have much experience in programming at all? How can one make sure you will continue developing this tool?

Second, nonetheless to my questions from First I would still like to mention here that I have an open PR over at the folder.view2 repo https://github.com/VladoPortos/folder.view2/pull/21 that I would like to see merged. You mentioned you didn't change that much (although 104 commits indicate otherwise), so it should be pretty easy to bring my changes over to this repo (you should be able to bring over my changes to your repo, without me having to open a pr at your repo).

Of course this would only matter if you really want to continue supporting this plugin in the long-term (it's annoying that we already need a v3 here) and if you are even interested in the changes I did in my PR.

I've got 2 questions for you too.

1. Why did you not ask VladoPortos of FolderView2 the same thing, it seems you are perfectly happy running FolderView2? The only difference between what he had done and what I have done is I disclosed the tool I used to help achieve a working plugin.

2. Is there any reason you prefer the approach of your PR instead of using the "hide update column" toggle? Afaik most compose users toggle this as it is irrelevant information to them. I'm happy to entertain feature requests once the bugs are ironed out (which they should almost be) but I'm not too keen on blending plugins for individual users. The compose side of things I'll look at because scolcipitato has it somewhat built in already but I would like to know why hiding the update column doesn't resolve your issue.
   Also the reason for so many commits is because of everything that needed fixing and yes I made a few visual improvements too https://github.com/chodeus/folder.view3/blob/main/CHANGELOG-fixes.md

   

The issue with compose is not necessarily solved by hiding the update column. Compose containers often times get highlighted in orange, to indicate an update, when there really is none. Of course, you can disable the highlighting in the folder settings, but then you break the update highlighting of normal docker containers in the same folder.

Just now, satchafunkilus said:

The issue with compose is not necessarily solved by hiding the update column. Compose containers often times get highlighted in orange, to indicate an update, when there really is none. Of course, you can disable the highlighting in the folder settings, but then you break the update highlighting of normal docker containers in the same folder.

Is there any benefit or is there anyone that would find a benefit with having the "orange text on update" on compose containers? Or is it pointless for compose containers and just a hangover as this was intended for dockerman containers? For clarity, I don't "run" compose, I have a test stack for this plugin.

Edited February 23Feb 23 by chodeus

Just now, chodeus said:

Is there any benefit or is there anyone that would find a benefit with having the "orange text on update" on compose containers? For clarity, I don't "run" compose, I have a test stack for this plugin.

Well if it would work correctly, I would love to have orange text on update for compose containers. If it's broken (and can't be fixed), I would much rather have the compose containers excluded from the orange highlighting alltogether.

1 minute ago, satchafunkilus said:

Well if it would work correctly, I would love to have orange text on update for compose containers. If it's broken (and can't be fixed), I would much rather have the compose containers excluded from the orange highlighting alltogether.

Yeah okay, I'm unsure if this is a compose manager plugin bug or a folderview plugin bug as I don't know why Unraid is seeing the compose container needing an update if it is in fact up-to-date but I'll take this onboard and do some research.

Joly0's PR replaces the apply update/up-to-date wording with "Compose" for folders that only have compose containers in them. Would this cause issues if you want to know when there's a valid update or do you not use the "apply update" button in the version column for updating compose containers?