mstrhakr

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

https://github.com/mstrhakr/compose_plugin

Thanks, If anything is breaking on main I can do a hotfix, otherwise it goes in the beta first, then pushed to main as a whole after lots of testing and some time for users to report things. Bugs still always make it through to the stable branch inevitably.

If you are willing, GitHub issues are always preferred for tracking these bugs and fixes. Things that aren't an Issue in GitHub might be missed or forgotten about.

Yea... There are a couple places that need fixed, the containers list just needs to be made scrollable. I'll fix this real quick in the dev branch, then I will push new beta later today with this fix.

So basically skip the new stack modal and just open the editor when adding a new stack, then automatically use the compose files project name as display name and folder name if not provided. That actually seems like a better UX than enter name, but makes it harder to do the external stack, albeit not by enough to matter.

yea, i have to figure out how to deal with this as its in an Iframe and i have limited control over it. i'm sure its possible but I havent looked at it yet. Should show done once the script is finished. I also want to add a setting to run an action without -d and the button would say detach in that case.

Deleting project folder should be happening unless its an external stack. I've added some additional failure handling to the dev branch (will be in beta soonish) to help if this is still happening. Creating a stack without a name doesn't work as that is how the folder is created. Currently only the name is required, description can always be skipped/left blank.

Adding https://plugin-docs.mstrhakr.com that I put together to try to bring all of this to one home. Hope it's useful to some of you, feel free to submit a PR or issue!

Hey all, I found this https://ca.unraid.net/submit and I'm wondering if anyone has used it. The starter template repo linked is private still so I'm assuming this is pending an announcement still, but it's live on the site so I wanted to ask here. Can find the button "Submit to Community Applications" at https://unraid.net/community/apps . It's below the sidebar menu options in the app browser iframe. On Mobile you have to open the menu to see it.

Thank you for letting me know, I will look into this.

I recently removed that 5.0.2 from the title bar as that is actually the Compose CLI version, not the plugin version. You can find the plugin version on the plugin tab if you are on stable, and in the beta I've moved both the plugin version and the Compose CLI version to the settings->credits page. Is this only happening for update, or do all foreground actions have the same problem?

I opened an issue on GitHub for this, this seems like it is worth doing but I have to look into it first of course. https://github.com/mstrhakr/compose_plugin/issues/98

Was this a one off issue or something you can consistently reproduce? What version were you on when you experienced this issue? I have fixed the issue I spoke about above and will be pushing it to the beta soon.

I can look into this, please open an issue on GitHub if you want me to actually remember lmao

After some brief testing, when a compose log window is open, and you run update (likely other options also) it takes over the log window and the popup is left empty. It runs the update in the existing new tab log window and does nothing with the popup ttyd. I will be looking into this, expect the fix to land in the beta first. The workaround is to ensure log windows are closed before performing actions or use run in background and grab the output after.

Does the update complete if you check run in background? That will tell us if the command is correct or not. Then I can check just the ttyd path. Do you have another ttyd window open, like a log window?

I submitted a PR here https://github.com/Squidly271/ca.update.applications/pull/2 pending Squid seeing it and merging or not.

This is a bug in CA Auto Update, it doesn't check the net.unraid.docker.managed label for dockerman, I'm looking into doing a PR on this but I need to validate this deeper into the docker.manager (built-in) plugin also. Basically at first glance, its checking ALL containers, regardless of the manger, so looking at the code its likely trying to update all 3rd party containers, not just compose managed ones. This would likely affect things like the Nextcloud All-In-One container that manages its own sub-containers. Anyone that knows more feel free to correct me. Easiest fix is to change it to only update the containers you want updated, instead of selecting update all.

I've been thinking about the custom start script, but I haven't heard anyone ask for custom scripts based on specific actions. Would you mind explaining your use case for me so I have a better understanding?

Funny you say that because I was recently pondering how one would create an XML based template for compose stacks to be able to pull them from the app store. But a merge/unification of docker+compose actually makes more sense than trying to fit this square peg of compose in the round hole of the CA App store. Until the day that happens or Limetech integrates this plugin, I will continue to try to improve this to meet the standards of integration. I always try to compare new features and improvements against what I think Limetech would want/do if this were integrated, like WWJD but instead its WWLTD lol.

You explained that all really well, thank you. I agree with all of it. My focus is on option 1 as I find options 2 and 3 to be way too much for this plugin. I can see option 1 working as an advanced feature or something but you make a lot of good points on the complexity of this. I especially appreciate the comments about frivolous support requests from uneducated users, as it seems that will be a problem forever with unraid. Seems like unraid attracts beginners, which isn't an issue, just something to be aware of. So I'll say it again, thanks for posting your thoughts on this, it is very appreciated. I'll have to think about it, I think limiting it to clone/pull only might work, but it still doesn't seem that needed when you can (for most compose files) just paste it into the editor. The advanced users could still do a git based stack manually so maybe we just leave it at that.

I can see this working, but I don't see a good way to do this AND allow users to have a git based single stack. This second use case is far more common as evidenced by all the major players offering it as an option (eg. komodo and the like). So with that said I likely will not be implementing this but there is now an open issue on GitHub you can comment on to show support.

This is likely a project name mismatch that didn't cause UI issues until this last update. If you run docker inspect immich_redis --format '{{ index .Config.Labels "com.docker.compose.project" }}' from the unraid terminal what does it give? Also what is your folder and display name set to? Once you run that command you can go to your project folder cd /boot/plugins/compose.manager/projects/[your immich project] then docker compose down -p [project name from first command]. Once that's done, the UI should stay in sync as it now uses the same project sanitizing function in the front end and back end.

Its on my to-do list, it will likely be in the next beta in the next few weeks. Comment on or like the GitHub issue for that feature request to show me which ones are important to you guys.