2 hours ago, primeval_god said:

In a future release an option to place the whole projects folder elsewhere will exist, no ETA.

Outstanding! Thanks for the reply.

What is the best way to handle updates with this plugin?

 

I have updates available.

 

 

Trying to update by clicking "apply update".

 

 

 

Updating the stack by clicking "Update stack" works.

 

 

However, it still shows "update ready" in the GUI. Very annoying. 

 

Something wrong or how can I mitigate this issue?

23 minutes ago, stagenet said:

Something wrong or how can I mitigate this issue?

Nope, just gotta live with the wrong "update ready".

5 minutes ago, Kilrah said:

Nope, just gotta live with the wrong "update ready".

 

Any way to disable them all together?

Edited February 16, 20242 yr by stagenet

Was possible to hide the "update ready" with FolderView plugin.

 

 

12 hours ago, stagenet said:

 

Any way to disable them all together?

https://github.com/unraid/webgui/pull/1582

This was just merged so I'd imagine it'll be coming in a release soon

 

Quote

 

Attention:

This application template has been blacklisted.

 

 

Should we be worried? Or are we just waiting for a plugin update?

 

15 minutes ago, 7hr08ik said:

 

 

Should we be worried? Or are we just waiting for a plugin update?

 

There seems to have been a glitch with Community Applications (my Tailscale plugin got blacklisted too), Squid is working on it. You shouldn't need to do anything.

On 2/15/2024 at 3:55 PM, Chris H said:

Hi all. 

 

New to unRAID and the Docker Compose Manager (not new to docker or containers or compose).

 

I didn't see this in the configuration but instructions might be elsewhere - how do I tell Docker Compose Manager to put the docker-compose.yml in a different directory than 

/boot/config/plugins/compose.manager/projects/

 

I apparently did this once but can't figure out how I did it so my compose files are stored there rather than where I can easily back them up.

 

Thanks in advance for any insight!

Check out the new release.

After I use Compose to create a container, it always prompts an update in the docker container interface, but the image is the latest version. I also encountered another problem, when Compose creates a container, there is a certain probability that the system docker will repeatedly create containers after starting docker, which leads to the containers created by Compose can not be used normally.

19 hours ago, primeval_god said:

Check out the new release.

 

I installed the new version but I don't see anywhere in settings for this. Can you point to how to set the global compose file location?

1 hour ago, Chris H said:

 

I installed the new version but I don't see anywhere in settings for this. Can you point to how to set the global compose file location?

It should be the first option on the setting page.

8 minutes ago, primeval_god said:

It should be the first option on the setting page.

Settings from the Apps entry for Docker Compose Manager takes me to the page to edit the stacks, not a settings page. I might have something messed up on my side.

 

I did also check for each stack but those settings haven't changed.

 

EDIT: I found it under the Settings for unRAID, down at the bottom. Thanks!

After updating to the latest version. Every time I update the configuration of one of my stacks I get the following message.

 

3 hours ago, stagenet said:

After updating to the latest version. Every time I update the configuration of one of my stacks I get the following message.

 

It should be fixed now.

7 hours ago, primeval_god said:

It should be fixed now.

 

Cheers!

On 2/16/2024 at 10:22 PM, primeval_god said:

I have no idea what this means.

thanks,It is already fixed now. Check the path of /tmp/plugins/pluginPending and remove the file of compose.manager.plg.

Cannot upgrade to the latest version ，The latest version is already 2024.2.20, but I can only upgrade to 2024.2.19。

 

9 hours ago, sarsmark said:

Cannot upgrade to the latest version ，The latest version is already 2024.2.20, but I can only upgrade to 2024.2.19。

 

Try uninstalling the plugin and reinstalling.

 

Does the Docker Compose MANAGER have a GitHub address? The download of downloads in the application market is always wrong.

I'm using the docker-compose-plugin and have the following problem...

Once a stack is using a network, the network will be displayed as the network-id and not as the network-name.

Can I fix this??

 

Thanks a lot

2 hours ago, tescher said:

I'm using the docker-compose-plugin and have the following problem...

Once a stack is using a network, the network will be displayed as the network-id and not as the network-name.

Can I fix this??

 

Thanks a lot

https://github.com/unraid/webgui/pull/1616

I've submitted a PR to address this. It's an issue with how unraid UI changed how it read the network. Hopefully this will be merged in soon. Feel free to edit your local files as per the pr to see if it works for you and also content on the pr.

Cheers

20 hours ago, sarsmark said:

 

Does the Docker Compose MANAGER have a GitHub address? The download of downloads in the application market is always wrong.

https://github.com/dcflachs/compose_plugin

3 hours ago, mtongnz said:

https://github.com/dcflachs/compose_plugin

thanks a lot。The next step is to solve the issue of prompt "apply update".

45 minutes ago, sarsmark said:

thanks a lot。The next step is to solve the issue of prompt "apply update".

Before you waste your time on this please note that any "fixes" are unlikely to be merged. I dont consider it to be an issue with this plugin. The problem is the same for any containers on the system created by means other than Dockerman (cli, portainer, composeman, etc.) thus the fix should be in Dockerman. Update tracking is not a feature of the compose manager plugin, and is in many cases irrelevant as locally built containers are a more common use case with compose.