Jump to content
Squid

[Plugin] CA Docker Autostart Manager

61 posts in this topic Last Reply

Recommended Posts

7 hours ago, Pegasy said:

Hi. I have the unraid docker added to a docker swarm and for some reason this plugin (CA docker autostart) lists all versions of each container even after they are removed from the "normal" unraid docker ui (and also don't show up using 'docker ps' in the terminal). 

 

Any idea how to either manually remove them or what can be done to exclude them? 

 

Screenshot of of all my docker containers currently 

Screenshot of the docker autostart manager list

The list is populated as soon as you enter the tab.  So, if you delete a container and then immediately switch to the manager, then the deleted container will still appear there.

 

Beyond that, the manager makes use of unRaid's management system, so if you are manually deleting containers at the command prompt, then the docker tab (and the manager) may or may not show the correct information.

 

But, quick comparision of your two screen shots shows that everything looks ok.  Admittedly I didn't zoom right in to compare all of the names from one shot to another.

Share this post


Link to post
10 hours ago, Squid said:

The list is populated as soon as you enter the tab.  So, if you delete a container and then immediately switch to the manager, then the deleted container will still appear there.

 

Beyond that, the manager makes use of unRaid's management system, so if you are manually deleting containers at the command prompt, then the docker tab (and the manager) may or may not show the correct information.

 

But, quick comparision of your two screen shots shows that everything looks ok.  Admittedly I didn't zoom right in to compare all of the names from one shot to another.

Look at the names in the 2nd screenshot, it has a lot of the dyndns service (dyndns_home, dyndns_home-root, dyndns_hostname, dyndns_unifi) all 2 times (atleast in view in that screenshot) where there first screenshot of the docker ui only shows 1 of each. The plugin list is also (as you can tell from the scrollbar on it) a lot longer, it has multiple pages of old swarm containers that has been removed from the unraid host (through a userscript which removes unused swarm containers), all those are gone from the unraid ui but show up in the plugin ui. 

Share this post


Link to post

You're probably looking at a caching error being made by Dynamix.  While I probably could fix this, this plugin is going to be deprecated for users that will be running the upcoming unRaid 6.6, as the bulk of it's functionality will be now included in the base OS

 

Share this post


Link to post
On 8/11/2018 at 4:20 PM, Squid said:

You're probably looking at a caching error being made by Dynamix.  While I probably could fix this, this plugin is going to be deprecated for users that will be running the upcoming unRaid 6.6, as the bulk of it's functionality will be now included in the base OS

 

Ok, perfect, then no worries :) 

 

Where can I read up on upcoming features? (just used unraid for a month or two so still trying to figure some stuff out / setting things up)

Share this post


Link to post
28 minutes ago, Pegasy said:

Ok, perfect, then no worries :) 

 

Where can I read up on upcoming features? (just used unraid for a month or two so still trying to figure some stuff out / setting things up)

I do not believe we have had any definitive news about what new features are coming in the next release.

Edited by itimpi

Share this post


Link to post
2 hours ago, itimpi said:

I do not believe we have had any definitive news about what new features are coming in the next release.

Not 100% true.  You can always look at the commit history on GitHub for the webUI to see what's coming at least in the UI itself.

  • Like 1

Share this post


Link to post
16 hours ago, Squid said:

Not 100% true.  You can always look at the commit history on GitHub for the webUI to see what's coming at least in the UI itself.

Just found - didn't know this existed.  Thanks

Share this post


Link to post

I desperately miss this plugin in v.6.6! The new version includes a timeout but it just starts containers alphabetically ... any idea how to do the whole "listen for port, then start" procedure now?

 

I just reinstalled the deprecated plugin out of desparation..

Share this post


Link to post
9 minutes ago, rix said:

it just starts containers alphabetically

Move the containers on the Docker page in the sequence you want them to start

  • Like 1

Share this post


Link to post

Is it really that simple?

 

Thanks for that reply O-O

 

Edit: This is perfect,... I feel stupid now. Maybe add a small note to the Help section for the next dummy to ask this!

Edited by rix

Share this post


Link to post
3 minutes ago, rix said:

Is it really that simple?

 

yes

  • Upvote 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now