Using wrong PHP version - 7.2.8 in use, needs PHP (>= 5.6, 7.0 or 7.1)

[Aterfax]

Project needs rebasing to a supported PHP version, as detailed here: https://docs.nextcloud.com/server/12/admin_manual/installation/source_installation.html

The usage of PHP 7.2 is causing errors:

Error	PHP	Function create_function() is deprecated at /config/www/nextcloud/lib/private/Route/Route.php#155	2018-09-15T05:03:16+0100

As explained further here:
nextcloud/server#6882 (comment)

PHP version therefore needs changing.

[aptalca]

You need to update your nextcloud

[Aterfax]

Not according to my dash:

[aptalca]

Not the image, the app

[Aterfax]

That isn't relevant to the docker being mis-configured and deploying the incorrect version of PHP (or the wrong version of Nextcloud depending on your point of view.)

*That is unless the docker is holding back the updates on my end for some reason.

[Aterfax]

Internal NextCloud updater was getting stuck on an extra file being present:

The following extra files have been found:
.rnd

No idea why this file is there or when it arrived but that would be a cause of desync in updates.

I was under the impression that this docker would keep NextCloud up to date of its own accord rather than require manual user input?

[j0nnymoe]

Nope, this is one of few containers we do that needs to be updated manually. See the first post on the unraid support thread https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/

[Aterfax]

I have no explanation for that random extra file locking the Nextcloud updater but since that is a simple file removal its not worth a ticket.

It being one of the rare manually updated, that'd be why its desync'd then. Cheers for the added clarity!

Might have been an idea to stick with PHP 7.1 for forward/backward compat but that's a bit late now.

Might be an idea to note for future re-basing or NextCloud version updates to try to retain a solution that works for both?

I'll leave this open for now so the @sparklyballs can have a read and then close.

It might also be an idea to make it obvious in big bold letters here: https://hub.docker.com/r/linuxserver/nextcloud/

That manual updates are needed as I see nothing mentioning that at present!

Might also need something that makes it obvious to users a docker image update has been pushed to support a new Nextcloud version that will need the app updating? Temporary index page?

[thelamer]

I have tested all trees of upgrading with success on our latest image.
I have dived deep into this container and Nextclouds offering. Ours will likely never be perfectly in sync from a php version standpoint. We will always use the system packages provided by Alpine.

Their update method in Docker is Unique and is kicked off by updating the base image with locks in place to ensure you cannot update from the WebUI.

I am picking up what you are laying down regarding keeping this up to date from major version changes as you may get stuck on an old version, but I do not see a solution to this problem that we can implement in our container as we have no input into their codebase.