Raboon

Whilst I'd prefer the Unraid team address this, I have an interim solution: Install the WebUI Custom CSS plugin Paste the below in both input boxes (ie light and dark mode) over the top of whatever's in there by default. @media (min-width: 1024px) { #displaybox .frame .grid { width: 1440px !important; } }

Cheers for the quick fix! I updated, tried to replicate both sets of steps again, and confirming the good news that I cannot. Restarting a group in the Dashboard now restarts the grouped containers. Pausing and resuming a group updates the group icon accordingly.

Hey @chodeus Nice one for continuing this plugin. Reaching out as clicking "Restart" on a Group of Docker containers on the Dashboard doesn't appear to work. To replicate: Head to the dashboard, click on a group of docker containers to display the list of options starting with "Expand". Start, Stop, Pause and Resume all work. Restart shows a brief red and orange loading icon, but none of the containers in the group are restarted as expected. No change. For reference, in the Docker tab, clicking a group of containers then clicking Restart from the options works as expected. A separate, small thing: Pausing a group doesn't update the Group's status icon. Click "Pause" on the same Group menu in the Dashboard. The individual containers update to show the yellow pause icon as expected. The group still shows the green play icon. So the group's status icon no longer matches the current state of the containers within it. Ideally the group's status icon would update to the pause icon, and back to play the play icon when clicking Resume. For reference, clicking "Stop" on the group does update the group icon to the red square icon. Thank you!

Following the updated dashboard page (which is great) there's a slight issue in Safari - the page is too wide for the view. That results in a scroll bar down the bottom of the page to pan it a tiny amount left and right. It's hardly mission critical... but it's scruffy, and hopefully an easy fix. This is on the default page zoom, with content blockers off. Currently on the latest version of Safari, but this has been visible since the update - previous versions of Unraid and Safari. Confirming that the page looks fine in Brave (but no, that's not the solution...). Unraid Version: 7.2.4 Saferi Version: 26.4 (21624.1.16.11.4) MacOS Version: 26.4 (25E246) Could you please make the page fit the view?

Exactly how the header should work. Nice one, thank you.

Pardon for not responding sooner, but thank you very much for figuring this out! Confirming that I'm now seeing legit updates to the container.

Thanks for looking into this further. Understood that you don't have an Unraid system for reference. To explain, the excerpt I sent was after seeing the notification "there's an update to this container! get it!". If I click update, I see that result. So, may I check: Unraid is looking at your docker hub for your images. https://hub.docker.com/r/mbentley/omada-controller/tags From there, for example, tag "5" was last pushed to Docker Hub 9 hours ago. So is it possible that Unraid's logic is: Unraid knows when the currently running image was pulled. When a user clicks on the "Apps" tab in Unraid, Unraid checks the date and time of the latest push in Docker Hub. If the push is after the pull, Unraid says "new image available!" I don't believe Unraid is looking at any manifests or digests when it flags an update is available. Only when the user triggers the update does it then state "this is all the same!" It'd be good to hear that confirmed by an Unraid guru. So you're saying Unraid should compare the time, and also the digest of an image to be sure a change in Docker Hub is worth being flagged as an update. And you're unable to suppress "meaningless" (not being rude) updates to the Docker Hub, because you rebuild everything by default, and can't capture "before this rebuild, this image started like this, after the rebuild, it ended up like this" and compare whether an image has changed meaningfully.

Understood, thanks for explaining. Glad that you're checking the current builds and updating them as necessary, for sure. But, like I said, builds are being rebuilt / reuploaded daily with no changes - Unraid shows: IMAGE ID [5]: Pulling from mbentley/omada-controller. IMAGE ID [dfd139f7c731]: Already exists. IMAGE ID [009aee103b7f]: Already exists. IMAGE ID [40e5127fbc58]: Already exists. IMAGE ID [53f40ed0171f]: Already exists. IMAGE ID [4f4fb700ef54]: Already exists. Status: Downloaded newer image for mbentley/omada-controller:5 TOTAL DATA PULLED: 0 B So the pipeline is currently triggering... unnecessary? rebuilds to certain images and updates that don't appear meaningful.

Hey @mbentley Thanks for the app. Understood about setting a version to avoid calamity. Starting about two-ish weeks ago, roughly once every 24 hours, Unraid flags that the Omada container has an update available. But, on triggering the update, it shows no changes. So the container just stops and restarts. Looking at the docker hub, all current images are being routinely updated, so at least Unraid isn't jumping at shadows. But can I check what's going on? This is seen using either the latest, or v5 tag. Thanks!