Am I interpreting this correctly? Why is the earlier version being installed? And is there a way around it, other than building a custom docker compose?
The problem is, that the imagick module needed to build the image is broken; it throws an error when building in 8.3 and aborts the build process.
Here the discussion about that:
That is the reason why all those out there creating images based on alpine-fpm are still using php8.2
All but Nextcloud All-In-One!
Since the bug has already been fixed in HEAD of the master branch on github, but nobody feels compelled to release it in PECL, I have developed a workaround for All-In-One that elegantly circumvents this problem. Therefore, Nextcloud All-In-One is the only Alpine-fpm based project that fully supports php8.3 at present.
Thanks for the info. I wasn’t aware of the problem.
I’m currently running Nextcloud on Truenas Core 13.3 with PHP83 (8.3.13) and php83-pecl-imagick-3.7.0_4. The NC version is 29.0.6, though I was running 30.0.1 up to about a week ago. I had to roll back because of an issue syncing calendars with caldav (issue below).
Everything was installed via package manager with no issues, and I’ve not noticed any problems with the application other than above which I believe is unrelated.
Core is for all intents EOL and I’m looking at moving to Scale and re-installing my apps on docker. Right now I’m trying to familiarise myself with how docker / docker-compose works and what’s involved in setting up my apps
Good to know about AIO. I had looked at it but I don’t need all the additional apps so was looking at a basic install. I may reconsider when I’m ready to move to Scale if the issue isn’t fixed by then. And hopefully the caldav issue will also be fixed so I can install the latest version. Otherwise, I’ll have to install 29.0.6.