It looks like your issue might be caused by a corrupted or incomplete Docker image, which can happen even if containers were not manually stopped. I’ve experienced similar behavior with the apache container in Nextcloud AIO, where they got stuck in the “starting” state without any obvious reason.
Here’s a method that has consistently worked for me and could help in your case:
Steps to resolve containers stuck in “starting”:
-
Open the Nextcloud AIO interface
– Stop all running containers. -
Go to Portainer (or use the CLI if you’re not using Portainer):
- Delete all stopped containers except for the
mastercontainer. - Identify the container that is stuck (e.g.,
apacheorredis) and delete its associated Docker image as well.
(In Portainer: Images > find the problematic one > remove it)
- Delete all stopped containers except for the
-
Let AIO recreate the container and download the image again.
– Go back to the AIO interface and wait for it to automatically pull a fresh copy and start the container. -
Optional: Clean up unused images once everything is working.
– In Portainer: Images > delete old and unused Nextcloud-related images to save space.
This approach has helped me recover from update issues or random startup problems without needing to restore full server backups. Give it a try — it’s a safe and clean method that might fix your issue with minimal disruption.
Note: This post was written with the help of an AI assistant as a writing aid only. The opinions, solutions, and technical recommendations are fully based on my personal experience.
More about how and why I use AI to write forum posts:
Is there limitations to installing Nextcloud via CT template on Proxmox - #4 by vawaver