mtongnz

@VladoPortos can I request we leave the docker label as folder.view? I don't see a need to change it as that only means we need to modify all our comps compose stacks. Cheers

There are 2x PRs that both address this in different ways. I went with a CSS only and JohannesHo went with a JS approach. Both work. My CSS approach - I also lined up the containers so they're all the same size. It's not the prettiest CSS but it works Mine: https://github.com/VladoPortos/folder.view/pull/12 JohannesHo: https://github.com/VladoPortos/folder.view/pull/11

I run a script to down then up each of my stacks in the order I want at array start. It works great: https://gist.github.com/mtongnz/f3ca13c7ff8472e54bbb7ff8cec265e1 This script also means I can add custom buttons into Folder View for each folder... I have each stack in it's own folder and a button for update, restart, down and up. Very handy

Install the User Scripts plugin. It comes with a script to auto remove orphan images. Set it to run on a schedule and it'll clean it up for you. It's an awesome plugin allowing php and bash scripts to be easily run from the ui.

I submitted a PR a while ago but it hasn't been merged yet. It fixes this issue. https://github.com/dcflachs/compose_plugin/pull/27

@phil1cI've just had a play with this... Think I've got it working. Try this PR & join the convo there: https://github.com/unraid/webgui/pull/1616 It fixes network name display, tweaks the IP & port mapping display, and fixes the webUI url generation.

Fix for 1 & 2: https://github.com/dcflachs/compose_plugin/pull/27 3 should work. Maybe try putting quotes around it

I put in a PR to fix this but it's not merged yet: https://github.com/dcflachs/compose_plugin/pull/27 You can manually modify the plugin and test it if you'd like.

Here's my PR to the unRaid webGUI git: https://github.com/unraid/webgui/pull/1616 It changes how networks, IPs and ports are displayed. Give it a try and let me know any thoughts

Here's my PR: https://github.com/dcflachs/compose_plugin/pull/27 This uses the existing functionality from the built in docker manager to do a check on compose manager stacks when they're run/updated and also has a manual check button. Fairly easy to modify your local server to try it out. Edit the files in /usr/local/emhttp/plugins/compose.manager as per the commits. If it's no good for you, revert by updating the compose manager plugin. Also this PR to "remove" update links for non DockerMan containers: https://github.com/unraid/webgui/pull/1582 This is a slightly different issue. The update link/button doesn't actually work for non DockerMan containers. This PR replaces those buttons with an update available message instead, leaving the update functionality to whatever is managing the container. Here's a gist for a User Script (get it from unRaid Community Apps). It allows you to call useful Docker Compose Manager functions via user script. These can be scheduled (note that if using a schedule, the defauts set at the top of the script will run). https://gist.github.com/mtongnz/f3ca13c7ff8472e54bbb7ff8cec265e1 This means you could set updates to automatically run on certain stacks if you wanted, or you can restart troublesome stacks (I called this down_up as that's what it actually is doing). I use it to start my stacks in a certain order when the array starts. Comments on these would be appreciated.

I have a feeling this is related to various other network display issues for non-dockerman containers (such as the correct network name not showing). This just got merged: https://github.com/unraid/webgui/pull/1616#issuecomment-2040820998 It shows multiple networks and the associated IPs. Ports seem to not correctly show which are internal and which are exposed for compose stacks at present - I'm currently working on a fix.

If you use the User Scripts plugin, I'd recommend my script here: https://gist.github.com/mtongnz/f3ca13c7ff8472e54bbb7ff8cec265e1 It lets you interact with this Compose Manager plugin via script and also run commands on multiple compose projects in a single command. Change line 5 (argumentDefault) and you can then schedule the command. I use it scheduled to "down_up" all my projects on array start - so it runs a down then an up on each stack. This ensures that all my dependencies start in the correct order as I was having issues when I left unRaid to autostart everything.

Sorry... Should've said docker containers. If they're on auto start, unraid starts them in whatever order it feels like

I had the same issue. Services seem to start in whatever random order unraid decides and this can break things. I wrote this script to address this: https://gist.github.com/mtongnz/f3ca13c7ff8472e54bbb7ff8cec265e1 I use the down_up action and run at array start and now it seems that everything works as it should. Male sure you edit line 5 of the script and list all the compose manager projects you'd like to restart - I doubt your project names match mine As a side note, I also disable all the auto start sliders on the docker page for any compose projects or the containers created by them.

https://github.com/dcflachs/compose_plugin