I've had 2 docker images update today and each time, when updating the docker images, it fails and removes the container totally.

 

I then go into apps, install the app again and it works perfectly, retaining all the settings?

 

I've checked the logs and this is the only warning I can see, but not sure what to do?

 

Feb 6 11:01:00 TechNAS [26693]: The command failed. Error: sh: /usr/local/emhttp/usr/bin/docker: No such file or directory<br>

 

Uninstall the advanced button plugin.  

 

You will have to though switch the docker page to advanced view, delete the orphaned containers

3 hours ago, Squid said:

Uninstall the advanced button plugin.  

 

You will have to though switch the docker page to advanced view, delete the orphaned containers

 

Thanks for the pointer.

 

I've done that, but I don't seem to see anything relating to 'orphaned containers'? Is there somewhere in particular I should be looking?

Docker tab, switch to advanced view in the top right.   You'll see all the orphans.  Click on then and you can remove them

3 minutes ago, Squid said:

Docker tab, switch to advanced view in the top right.   You'll see all the orphans.  Click on then and you can remove them

 

This is what I'm seeing...?

 
This is what I'm seeing...?

By reinstalling you probably got rid of the orphans already as a side effect

12 hours ago, Squid said:

By reinstalling you probably got rid of the orphans already as a side effect

 

Great. I'll keep an eye on things.

 

Thanks for your help!

Thanks, this thread fixed my problem as well.

I have a similiar problem.

 

After I edited dockers, (maybe i messed up something, and it didn't start) they went missing, and 'became' an orphan image.

I've been using unraid for over a year now, it never happened in 6.3.x

few days ago I updated to 6.4.1, and it started happening (could be unrelated)

 

what could cause this?

 

what is an orphan image anyway? why can't I just edit the xml, it wasn't from a template

18 minutes ago, LSL1337 said:

what could cause this?

The Advanced Buttons plugin - remove it

 

18 minutes ago, LSL1337 said:

what is an orphan image anyway

A failed docker install

23 minutes ago, LSL1337 said:

After I edited dockers, (maybe i messed up something, and it didn't start)

Misread the post, and I'm so used to saying uninstall advanced buttons plugin about a million times a day its become the standard opening for any of my posts.  But, if you do have it installed, get rid of it.  Please save my keyboard the wear and tear.

 

In your case, since you said "edited" dockers, what happened is that you made a mistake, and the container failed to start.  The error that you made would have been listed beneath the docker run command.

Edited March 14, 20188 yr by Squid

But before that, If I edited, and it failed to start, it would be still there, to fix the docker start up settings.

I will remove the plug-in

I hope it will fix it!

 

thanks!

2 minutes ago, LSL1337 said:

I will remove the plug-in

 

unRAID 6.5 adds the possibility to upgrade, start and stop ALL containers with a single button.

Actually unRAID 6.5 is a recommended upgrade to address the Meltdown and Spectre vulnerabilities.

 
unRAID 6.5 adds the possibility to upgrade, start and stop ALL containers with a single button.

Ooooh, missed that bit. Nice.

Sent from my LG-H815 using Tapatalk

19 minutes ago, LSL1337 said:

If I edited, and it failed to start, it would be still there, to fix the docker start up settings.

Yeah, the template should still be there and accessible via Apps, Previous Apps section

I don't have the advanced buttons plugin installed, but are getting the same issue. It seems to happen when the auto update of the dockers occur. It happens like once or twice a month. The docker disappears and become and orphan... Anyone know what the problem could be+