Attempt to Delete Orphan Images Multiple Times During Docker Update Process

When there are multiple containers installed and an update is processing there is an attempt after the first container updates to delete the existing image, which fails because the image is still in-use by alternate instances. The updates continue to the next instance, however there is never another attempt to see if that existing image can now be deleted resulting in (orphan image)'s that must be manually removed and require the Advanced View to even see.

It would be ideal for the system to handle multi-instance container maintenance as effortlessly as it does solo containers.