Nextcloud and Apache Containers Never Fully Start (Marketplace App AIO)
I'm attempting to deploy a Nextcloud instance via the marketplace app, and the nextcloud and apache containers will not fully start. The logs say the apache container is waiting on the Nextcloud container to start, and the nextcloud container is unable to authenticate the password for the oc_nextcloud user, then states it is waiting for the database to start. The database log says the nextcloud_database does not exist, that password authentication has failed for the same user oc_nextcloud, and that role does not exist. I have experience with nextcloud deployed through snap, but not as a docker. I have tried the installation twice and had the same issue arise, it does not go away leaving the server running for several days. I can't find anything specific about it online, and would just like to find a solution, or I may just deploy a Ubuntu instance and install it via snap instead.
1 Reply
tlambert
Linode Staff
Hey @Lionon!
I've run a few tests with our Nextcloud App from the Marketplace. Each time the application has deployed successfully. I have noticed that, at first, the Apache and Nextcloud containers will have yellow circles next to them and be marked as "Starting". However, once I refresh the page, they change to "Running".
I'll also suggest following along with the installation process in the Linode Shell (Lish) to make sure it's finished before you attempt to connect to your Nextcloud server. It should take 5-7 minutes to complete, but I was giving it 7-9.
It's also worth noting that the Linode documentation says all plan sizes can be used, the Nextcloud system requirements suggest more resources if you're using any of the optional addons:
Minimal system requirements: When any optional addon is enabled, at least 2GB RAM, a dual-core CPU and 40GB system storage are required. When enabling ClamAV or Fulltextsearch, at least 3GB RAM are required. When enabling everything, at least 4GB RAM are required. Recommended are at least 1GB more RAM than the minimal requirement.
If you've selected any of the optional addons and your plan size is smaller than suggested, it's possible your issue is related to resource requirements.
I hope this helps!