[Plugin] Docker Compose Manager


Recommended Posts

On 5/9/2022 at 1:56 AM, primeval_god said:

Support for specifying WebUI and Icons via docker labels is coming i believe in unRAID 6.10. Likewise i plan on adding some functionality to this plugin to support automatically inserting the necessary labels into compose files.

 

Welp, the menu I have been skipping over the whole time was the one thing I was about to come ask about. Works fantastic. Have switched every single one of my docker containers over to compose (with help of Composerize).

 

Edit:

 

I notice only .png are working for the icons. Using an .svg displays a blank icon. This differs from Docker Folders which accepts both. Is this intentional?

Edited by Lebowski89
Link to comment
7 hours ago, Lebowski89 said:

I notice only .png are working for the icons. Using an .svg displays a blank icon. This differs from Docker Folders which accepts both. Is this intentional?

That is a Dockerman question. The compose plugin only assigns the labels to the containers. Unraid's builtin Dockerman is what actually reads the label and caches/displays the icon.

  • Like 1
Link to comment

i've searched in the thread but can't really find it addressed too much but how do people go about mass updating their containers? i understand that the update stack button works and is great but its a bit cumbersome when you have to do that 30-40 times, rather than a single button press

what solutions have people come to, to automate this? or is this something that could be added natively to the plugin?

edit: seems watchtower is the solution that is posited in the previous page so i'll give that a shot

Edited by mrpops2ko
Link to comment

Getting some label UI oddities here and there. For example, with Traefik, I've put the correct URL (http://192.168.##.##:port) in the Web UI column but it opens the localhost IP without a port. Then for Whisparr the WebUI is also correct, but when you open it the IP you've entered is doubled (http://192.168.##.##/192.168.##.##:port). Have tried stack down, up, updated, deleted containers, etc.

 

 

 

Link to comment
5 hours ago, Lebowski89 said:

Getting some label UI oddities here and there. For example, with Traefik, I've put the correct URL (http://192.168.##.##:port) in the Web UI column but it opens the localhost IP without a port. Then for Whisparr the WebUI is also correct, but when you open it the IP you've entered is doubled (http://192.168.##.##/192.168.##.##:port). Have tried stack down, up, updated, deleted containers, etc.

The changes you are making are likely not taking effect. There is a long standing issue with how dockerman handles the webui and icon labels. Basically it caches them the first time a container is seen and subsequent changes dont have an effect. Try restarting your server, that may fix the webui label issues.

  • Like 1
Link to comment
10 hours ago, kiwijunglist said:

This doesn't seem to be available anymore under community apps.

 

I installed using docker-compose-manager plugin.

 

Add new stack, name it vorta.

Is there a question here? I dont really understand the post. 

Link to comment
10 hours ago, primeval_god said:

Is there a question here? I dont really understand the post. 

 

Hi sorry, It looks like I posted in the wrong thread.  Vorta is no longer available in community apps.  I meant to post that in the vorta-docker thread.  Sorry.

Link to comment

After deploying docker-compose using the plugin, when a container has an update, when I update the container using the compose plugin, there is still a constant update reminder in the webui docker interface. The only solution I currently feel is to down from the plugin interface, then delete the container, and then open the prompt to update the project. Automatically start and restart NAS

Link to comment
4 hours ago, unraid_fk34 said:

So I'm having issues displaying the custom network name in the docker containers tab. It will only show me the ID. I found a thread discussing this particular issue on the forums. Is that something that has to do with unraid or the plugin? Is it something that could be fixed in the future or is there a solution maybe?

The issue is with unRAID not this plugin. Last I was aware there was an open PR fixing the issue.

Edited by primeval_god
Link to comment
15 hours ago, pteromyini said:

Is there any way to modify it? As a person with obsessive-compulsive disorder, it is very uncomfortable to see it

This was driving me crazy as well. It's quite convenient to rely on the container update checks to determine when to update the compose stacks.

 

From what I could gather the file /var/lib/docker/unraid-update-status.json holds the update status for the images. When there is no template for a container that data is never updated and gets stale. It should be fixed at some point but for now you can delete that file and "Check for Updates" in the webui to force a recheck.

Edited by dlawisch
typo
Link to comment
On 4/18/2024 at 4:41 AM, dlawisch said:

This was driving me crazy as well. It's quite convenient to rely on the container update checks to determine when to update the compose stacks.

 

From what I could gather the file /var/lib/docker/unraid-update-status.json holds the update status for the images. When there is no template for a container that data is never updated and gets stale. It should be fixed at some point but for now you can delete that file and "Check for Updates" in the webui to force a recheck.

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.

 

 

Edited by mtongnz
Add second PR & GIST
Link to comment
On 4/16/2024 at 9:10 PM, unraid_fk34 said:

So I'm having issues displaying the custom network name in the docker containers tab. It will only show me the ID. I found a thread discussing this particular issue on the forums. Is that something that has to do with unraid or the plugin? Is it something that could be fixed in the future or is there a solution maybe?

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

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.