April 29, 20251 yr Author Just now, Gorden said: I cant find it anywhere in the terminal log but when I check the project folder I see a file called version and when I check what's inside it says 1 Ah no i meant, if you run the command "docker compose version" in terminal what does it output.
April 29, 20251 yr root@:~# docker compose version docker: 'compose' is not a docker command. See 'docker --help' root@:~# docker-compose version docker: 'compose' is not a docker command. See 'docker --help' root@:~# docker.compose version bash: docker.compose: command not found root@:~# plugin Process plugin files. I am trying to figure out what's the right command for it but not sure if the picture will say what you requested
April 29, 20251 yr Author 1 minute ago, Gorden said: root@:~# docker compose version docker: 'compose' is not a docker command. See 'docker --help' root@:~# docker-compose version docker: 'compose' is not a docker command. See 'docker --help' root@:~# docker.compose version bash: docker.compose: command not found root@:~# plugin Process plugin files. I am trying to figure out what's the right command for it but not sure if the picture will say what you requested No you got it, the first was the correct command. It looks like compose (as in the docker compose package not the compose manager plugin) is not being found. I suspect this may be an issue with this plugins compatibility with unRAID 7.1.0-rc3 (which has not been tested yet). I will try and look into this further tonight. Thanks for your help.
April 29, 20251 yr Much appreciate it for your hard work!! and sorry for not mentioning my unraid version from the start!
April 30, 20251 yr Author 8 hours ago, Gorden said: Much appreciate it for your hard work!! and sorry for not mentioning my unraid version from the start! I pushed an update to the plugin. I am not sure that if it will do anything to fix your issue, but could you try it out and report back?
April 30, 20251 yr 13 hours ago, primeval_god said: I pushed an update to the plugin. I am not sure that if it will do anything to fix your issue, but could you try it out and report back? I just did it still wont recognize compose command for some reason it might be an issue from my end? I am going to uninstall and restart the server and do a fresh install
April 30, 20251 yr root@host:~# docker compose version docker: 'compose' is not a docker command. See 'docker --help' root@host:~# still wont recognize it
May 1, 20251 yr Author 22 hours ago, Gorden said: root@host:~# docker compose version docker: 'compose' is not a docker command. See 'docker --help' root@host:~# still wont recognize it I pushed another update for you to try.
May 1, 20251 yr thanks for ur effort after the latest update, ive got one of my stacks broken not working idunno why tho still creating the offspring containers successfully but the main compose stack is still red not working properly am on latest rc unraid any help would be appreciated BTW dozzle cant see the created containers at all TIA Edited May 1, 20251 yr by drahmed86
May 1, 20251 yr Author 2 hours ago, drahmed86 said: thanks for ur effort after the latest update, ive got one of my stacks broken not working idunno why tho still creating the offspring containers successfully but the main compose stack is still red not working properly am on latest rc unraid any help would be appreciated BTW dozzle cant see the created containers at all TIA Were you previously able to create, destroy, and update stacks on unRAID 7.1.0-rc3? What do you see on the in the terminal if you run the command "docker compose version"? Have you tried bring the stack down and then back up?
May 2, 20251 yr 13 hours ago, primeval_god said: I pushed another update for you to try. Thank you so much for your hard work. Unfortunately the issue is still there. Tried update stack, compose up... nothing. I even typed in docker compose version and still wont recognize it. docker: 'compose' is not a docker command.
May 2, 20251 yr I have just updated my unraid to rc4. Still the facing the same issue! I think I am going to do a full reset on my usb because there has to be something that is messing up with my interface
May 2, 20251 yr Just now, Kilrah said: Did you try uninstalling/reinstalling the plugin yet? Yep I even removed it from the boot config file to confirm the uninstall
May 2, 20251 yr Author 2 hours ago, Gorden said: Yep I even removed it from the boot config file to confirm the uninstall Did you do a full system reboot between uninstall and reinstall? Thats typically required to fully uninstall a plugin.
May 2, 20251 yr 2 hours ago, primeval_god said: Did you do a full system reboot between uninstall and reinstall? Thats typically required to fully uninstall a plugin. I just did and still ended up with the same results. I am doing a full back up of my data because I am definitely doing a full system reset. Don't really want to waste your time on me I really apologize for taking so much of your time just to find out that's its something from my end which I really don't know about. And thank you so much for your full focus support on me.
May 4, 20251 yr Once again thank you very much for this beautiful and amazing compose plugin it made life so much easier! I have one question. how to use extra parameters --u 99:100 in the compose? or in general how to do extra parameters? I tried creating a nextcloud compose with mariadb but the permissions seems off I was pretty sure it was working last night but had to do chown -R method but i dont think that fixed it.
May 5, 20251 yr Author 20 hours ago, Gorden said: Once again thank you very much for this beautiful and amazing compose plugin it made life so much easier! I have one question. how to use extra parameters --u 99:100 in the compose? or in general how to do extra parameters? I tried creating a nextcloud compose with mariadb but the permissions seems off I was pretty sure it was working last night but had to do chown -R method but i dont think that fixed it. "Extra Parameters" is dockerman terminology for the box that allows you to specify command line flags to be added to the docker run command (typically for options that dockerman does not natively support). Generally speaking you would have to lookup the specific option you are trying to use in the compose file reference. In this case i think the -u option is equivalent to to adding the "user" element to containers in your compose file. https://docs.docker.com/reference/cli/docker/container/run/ https://docs.docker.com/reference/compose-file/services/#user Edited May 5, 20251 yr by primeval_god
May 5, 20251 yr Got it!! so the way it worked was: user: 99:100 and in terminal chown -R nobody:users /path/to/appconfig Thanks! Edited May 5, 20251 yr by Gorden
May 13, 20251 yr On 2/1/2024 at 3:51 PM, primeval_god said: The requirements for the icons are the same as those of unRAID's Dockerman ui (whatever they are). All the compose manager does is apply a label to each container with the icon url you specify. Everything after that is built in unRAID webui functionality. There is a known issue where updating the icon url does not actually change the icon of that container (thus you kind of only have one shot at specifying the icon). The problem is with the way dockerman downloads and caches icons. I attempted a pull request for a fix but never got any traction. You can manually go in and delete the cached icons to force unRAID to redownload them. I've been able create a brand new container and specify its icon, and also change that icon later by manually deleting the cached icons, but what I can't quite figure out is how to *add* an icon to an existing container that was originally created without any icon label. Adding the label and compose down/up doesn't seem to work. Any ideas on forcing an icon in this scenario?
May 13, 20251 yr Author 21 minutes ago, so7ow said: I've been able create a brand new container and specify its icon, and also change that icon later by manually deleting the cached icons, but what I can't quite figure out is how to *add* an icon to an existing container that was originally created without any icon label. Adding the label and compose down/up doesn't seem to work. Any ideas on forcing an icon in this scenario? Its been a while since I thought about this issue, so please forgive me if my memory is a bit off. If i remember correctly the absence of a specified icon means the container gets a copy of the default question marked icon cached. I think you have to go in and remove the cached icon to force it to actually pull a new icon. Edit i did not remember correctly. Edited May 13, 20251 yr by primeval_god
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.