October 20, 20223 yr Author 15 hours ago, Beermedlar said: Is there a way to know docker images have new verison? No not at this time.
October 22, 20223 yr How do I update docker images using this? also, on bottom of docker tab is normal for when this plug is installed to say this: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32 at the bottom of the docker tab?
October 23, 20223 yr Author 17 hours ago, blaine07 said: How do I update docker images using this? Use the update stack button on the docker compose page. 17 hours ago, blaine07 said: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/compose.manager/php/compose_manager_main.php on line 32 at the bottom of the docker tab? This is not normal. What OS version are you using? Is your plugin up to date? Do you have the docker folder plugin installed?
October 23, 20223 yr Just now, primeval_god said: Use the update stack button on the docker compose page. This is not normal. What OS version are you using? Is your plugin up to date? Do you have the docker folder plugin installed? Ok on update. OS- 6.11.1 Plugin up to date and yes docker folder plug-in installed.
October 25, 20223 yr Is there a way to auto update containers with a shedule like auto update aplications plugin does?
October 26, 20223 yr Author 15 hours ago, L0rdRaiden said: Is there a way to auto update containers with a shedule like auto update aplications plugin does? This plugin does not provide such a thing. If you really want auto-updating for docker containers i would look into something like Watchtower.
October 26, 20223 yr On 10/23/2022 at 12:22 PM, primeval_god said: Use the update stack button on the docker compose page. This is not normal. What OS version are you using? Is your plugin up to date? Do you have the docker folder plugin installed? Any other ideas on this error thing mate?
October 26, 20223 yr Author 2 hours ago, blaine07 said: Any other ideas on this error thing mate? Would you be willing via PM to provide me with a list of Stack Names as well as the names of the project folders in which they reside (and any indirect paths that are used)?
October 26, 20223 yr 2 minutes ago, primeval_god said: Would you be willing via PM to provide me with a list of Stack Names as well as the names of the project folders in which they reside (and any indirect paths that are used)? LITERALLY didn't have it installed until this guide sent me here a few days ago; I followed this guide: https://mfaz.dev/posts/immich-unraid/
October 27, 20223 yr It is documented somewhere all the labels available? Why when I click on ok the popup disapear and nothing happens? It's because is a still a empty docker compose? do I have to populated the compose yaml first? What is the plan for unraid regarding docker compose? will they integrate it better or provide official support? having compose doesn't make sense use "dockerman", everything should be based on compose even if we have Unraid WEBUI on top. It would be easier to use and administrate and It is the market standard.
October 27, 20223 yr Author 1 hour ago, L0rdRaiden said: It is documented somewhere all the labels available? Why when I click on ok the popup disapear and nothing happens? It's because is a still a empty docker compose? do I have to populated the compose yaml first? You must define containers in your compose yaml first. Once you do this the popup will show options for which labels can be modified. 1 hour ago, L0rdRaiden said: What is the plan for unraid regarding docker compose? will they integrate it better or provide official support? having compose doesn't make sense use "dockerman", everything should be based on compose even if we have Unraid WEBUI on top. It would be easier to use and administrate and It is the market standard. To my knowledge there is no plan to officially integrate compose support into unRAID. Dockerman is the official unRAID method of administering docker and is unlikely to go anywhere.
October 27, 20223 yr Author 20 hours ago, blaine07 said: LITERALLY didn't have it installed until this guide sent me here a few days ago; I followed this guide: https://mfaz.dev/posts/immich-unraid/ Unfortunately I am unable to reproduce the issue on my local machine. It could be due to the docker folder plugin as i dont use it or test compatibility with it. There is also a chance it has something to do with unRAID 6.11.1 as I am still using 6.9.3 and dont directly test against newer versions. That said this is the first i report of the issue I have seen and I have no idea of what the distribution of unRAID versions this plugin is being run on. One other question, do you have any compose stacks running on your system that were not created through the compose plugin webui?
October 28, 20223 yr 11 hours ago, primeval_god said: Unfortunately I am unable to reproduce the issue on my local machine. It could be due to the docker folder plugin as i dont use it or test compatibility with it. There is also a chance it has something to do with unRAID 6.11.1 as I am still using 6.9.3 and dont directly test against newer versions. That said this is the first i report of the issue I have seen and I have no idea of what the distribution of unRAID versions this plugin is being run on. One other question, do you have any compose stacks running on your system that were not created through the compose plugin webui? No. Literally only that link above. Sadly I’m too stupid to get very far “out in the weeds” lol
October 31, 20223 yr Every time after I update stack for new images, I need to do 2 extra steps below. Could this be automated so its behavior is more integrated with Unraid dockerman? Manually remove orphaned image. Manually update image local digest in /var/lib/docker/unraid-update-status.json (taking traefik as an example), so Unraid dockerman stops saying update ready. "library/traefik:latest": { "local": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "remote": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "status": "true" }
October 31, 20223 yr 4 minutes ago, sjtuross said: Every time after I update stack for new images, I need to do 2 extra steps below. Could this be automated so its behavior is more integrated with Unraid dockerman? Manually remove orphaned image. Manually update image local digest in /var/lib/docker/unraid-update-status.json (taking traefik as an example), so Unraid dockerman stops saying update ready. "library/traefik:latest": { "local": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "remote": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "status": "true" } Does this to me too but I wasn’t smart enough to fix it or work around it lol
November 5, 20223 yr I have created my container stacks via Portainer, which works great. My problem is that the stacks do not automatically start after I reboot the server. I have to manually start each stack from within Portainer. Does someone know a solution for this? Edit: Nevermind, I simply had to check the Autostart option in the Docker tab of the Unraid WebGUI. Edited November 5, 20223 yr by EuleMitKeule
November 5, 20223 yr On 10/7/2022 at 6:18 PM, swallace said: For example, here is my stack UI Label config: And here is the resulting URL I'm taken too when I click on the WebUI in the GUI: Is there any way to get around this? EDIT: Looks like I just need to add http:// before the IP. Duh Did prepending "http;//" really solve this problem? I'm currently tinkering with Docker Compose Manager and encountering the same problem regardless of what I type in the web UI field. I have already tried things like: http://[IP]:[PORT:1234] http://[IP]:[PORT] [IP]:[PORT:1234] 12.34.56.78:1234 :[PORT] :1234 [PORT] 1234 Clicking on the web UI button takes me to: http://<unRAID-server-IP>/<unRAID-server-IP>:<host-port-of-container>
November 6, 20223 yr On 10/30/2022 at 10:09 PM, sjtuross said: Every time after I update stack for new images, I need to do 2 extra steps below. Could this be automated so its behavior is more integrated with Unraid dockerman? Manually remove orphaned image. Manually update image local digest in /var/lib/docker/unraid-update-status.json (taking traefik as an example), so Unraid dockerman stops saying update ready. "library/traefik:latest": { "local": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "remote": "sha256:4c388f477f5b7aa48420694d90db0ecb96b4ecede60b9b7589c87858abf87b60", "status": "true" } Sorry, I know this is a lot, but can you provide any instructions on how you're doing this exactly?
November 6, 20223 yr 28 minutes ago, blaine07 said: Sorry, I know this is a lot, but can you provide any instructions on how you're doing this exactly? Maybe use watchtower?
November 6, 20223 yr Author 20 hours ago, frah said: Did prepending "http;//" really solve this problem? I'm currently tinkering with Docker Compose Manager and encountering the same problem regardless of what I type in the web UI field. I have already tried things like: http://[IP]:[PORT:1234] http://[IP]:[PORT] [IP]:[PORT:1234] 12.34.56.78:1234 :[PORT] :1234 [PORT] 1234 Clicking on the web UI button takes me to: http://<unRAID-server-IP>/<unRAID-server-IP>:<host-port-of-container> You do need to have the http:// portion of the address as well as the the IP and port numbers of your server. Also the [IP]:[PORT] syntax of dockerman will not work in the compose plugin.
November 6, 20223 yr 2 hours ago, primeval_god said: You do need to have the http:// portion of the address as well as the the IP and port numbers of your server. Also the [IP]:[PORT] syntax of dockerman will not work in the compose plugin. Thanks for your reply @primeval_god if I enter http://10.0.10.32:80 or http://10.0.10.32 80 the WebUI button opens a new tab with the URL http://10.0.10.32/10.0.10.32:80.
November 8, 20223 yr First reboot since installing Compose Manager (updated Unraid to 6.11.2), boot hangs due to error: grep: /boot/config/plugins/compose.manager/compose.manager.cfg: No such file or directory Resolved by booting in safe mode and manually creating the config file with default values: OUTPUTSTYLE="ttyd" PATCH_UI="false" DEBUG_TO_LOG="false"
November 8, 20223 yr Firstly thanks for this plugin I'm new to unraid but the Docker UI is horrible. As I use traefik there's quite a few labels that I maintain, adding them one by one is awful. And containers like littlelink-server that use entirely variables, oh man, it would take me 20 minutes just to type them all in. I know the answer to this is probably no, but is there anyway to stop unraid flagging all the composer containers as requiring an update, as that's triggering notifications and makes the docker UI hard to follow when it says there are updates to install that there aren't. If not is there any alternative UI to creating docker containers in unraid that isn't an awful experience? EDIT: Found the patch UI setting which seems to take care of the docker UI. I found in common problem fixer you can ignore a specific warning, so have just set them to ignored. Not ideal but better than it was Edited November 8, 20223 yr by PhilBarker
November 10, 20223 yr On 10/27/2022 at 3:21 PM, primeval_god said: Unfortunately I am unable to reproduce the issue on my local machine. It could be due to the docker folder plugin as i dont use it or test compatibility with it. There is also a chance it has something to do with unRAID 6.11.1 as I am still using 6.9.3 and dont directly test against newer versions. That said this is the first i report of the issue I have seen and I have no idea of what the distribution of unRAID versions this plugin is being run on. One other question, do you have any compose stacks running on your system that were not created through the compose plugin webui? Same issue here with a Mealie stack......happened after the last Unraid update I think....
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.