[Bug]: Upgrade from 32.0.3 to 32.0.4 failed

[isZYKerman]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

My 32.0.3 instance runs well. After pulling the 32.0.4 and firing the containers up I got errors and the container just restarted forever.

Steps to reproduce

1. Find a running 32.0.3 instance
2. Upgrade it to 32.0.4

Expected behavior

Upgrading process should be successfully finished.

Nextcloud Server version

32

Operating system

Other

PHP engine version

Other

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Updated from a MINOR version (ex. 32.0.1 to 32.0.2)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

N/A

List of activated Apps

N/A

Nextcloud Signing status

N/A

Nextcloud Logs

N/A

Additional info

I use docker for my services. The php engine, web server, etc. are shipped within in the image. The docker logs -f nextcloud-app-1 output:

Can't start Nextcloud because the version of the data (
Warning: Invalid "upload_max_filesize" setting. Invalid quantity "10240M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Invalid "post_max_size" setting. Invalid quantity "10240M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Invalid "memory_limit" setting. Invalid quantity "4096M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Failed to set memory limit to 0 bytes (Current memory usage is 2097152 bytes) in Unknown on line 0
32.0.3.2) is higher than the docker image version (
Warning: Invalid "upload_max_filesize" setting. Invalid quantity "10240M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Invalid "post_max_size" setting. Invalid quantity "10240M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Invalid "memory_limit" setting. Invalid quantity "4096M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0
Warning: Failed to set memory limit to 0 bytes (Current memory usage is 2097152 bytes) in Unknown on line 0
32.0.4.1) and downgrading is not supported. Are you sure you have pulled the newest image version?

Then the same content just repeats as the container restarts. It seems like a mixture of warnings for several "invalid" settings and a failure of upgrade because it thinks that 32.0.4 is a lower version than 32.0.3.🤣
For referrence, here is my compose file for the nextcloud-app-1 service:

  app:
    image: nextcloud:32.0.4
    container_name: nextcloud-app-1
    restart: unless-stopped
    ports:
      - 30030:80
    depends_on:
      - db
      - redis
      - onlyoffice
      - push
    volumes:
      - /mnt/Data/AppData/nextcloud/ncdata/:/var/www/html
      - /mnt/Data/TANK:/mnt/Data/TANK
      - ... # other external storages
    environment:
      - MYSQL_PASSWORD=***
      - MYSQL_DATABASE=nextcloud
      - MYSQL_USER=nextcloud
      - MYSQL_HOST=db
      - PHP_MEMORY_LIMIT=4096M
      - PHP_UPLOAD_LIMIT=10240M
      - OPcache=1024M
      - APACHE_BODY_LIMIT=0
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:80"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 5s
    networks:
      - nc_net
    extra_hosts:
      - "host:host-gateway"

[joshtrichards]

Then the same content just repeats as the container restarts. It seems like a mixture of warnings for several "invalid" settings and a failure of upgrade because it thinks that 32.0.4 is a lower version than 32.0.3.🤣

The first is leading to the second.

The cause of the first is something in your environment:

Invalid quantity "10240M": value is out of range, using overflow result for backwards compatibility in Unknown on line 0

That error is from PHP not Nextcloud. I believe it mostly comes up when the memory quantity exceeds what is available or possible on the underlying host.

The second matter: that particular image's entrypoint uses PHP to retrieve some bits (like installed/target Nextcloud version strings). However the first matter is causing PHP to not run in your environment so the version check effectively fails. A variation was in #2509; #2512 should address it when/if it gets merged.

But your core issue is unlikely to be a bug; it's more likely something environmental.

[isZYKerman]

Well I'm kind of confused.🤔 I'm on a machine with 32GB memory so resources shouldn't be the problem. I don't know what does it mean by "value is out of range".


In the official document the upload limit was (as an example) set to 16GB and the RAM was recommended to be at a minimum of 512MB per process. NONE of these mentioned a quantity limit in value. As these configurations work for 32.0.3 but not 32.0.4, there must have been a change in something that caused this issue. If we can find the documents on the "change", it will be easier to solve the problem.

[acidicX]

I'm facing the exact same issue. Deployment is done via k8s (nextcloud's own helm chart), we are using the fpm-alpine image. The server definitely has enough RAM.

@joshtrichards did anything get bumped on the PHP (fpm) or alpine side between 32.0.3 and 32.0.4 images?

[joshtrichards]

Can you confirm the locally pulled image isn't i386?

docker image inspect <image_name_or_id> --format '{{.Os}}/{{.Architecture}}'

My best guess at the moment is that you pulled before all the architectures were built and got a fallback one instead. But that's just a theory.

[acidicX]

Since I did a downgrade after the failure, I cannot verify this anymore. I just upgraded to 32.0.5 and that seems to work now.

[mdartmann]

Upgrading from 32.0.2 to 32.0.5 (I also tried 32.0.4 in the past but had to downgrade) fails for me as well:

app-1  | Can't start Nextcloud because the version of the data (
app-1  | Warning: PHP Startup: Unable to load dynamic library 'memcached' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached.so (Error relocating /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached.so: igbinary_unserialize: symbol not found)) in Unknown on line 0
app-1  |
app-1  | Warning: PHP Startup: Unable to load dynamic library 'redis' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis.so (Error relocating /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis.so: igbinary_serialize: symbol not found)) in Unknown on line 0
app-1  | 32.0.2.2) is higher than the docker image version (
app-1  | Warning: PHP Startup: Unable to load dynamic library 'memcached' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached.so (Error relocating /usr/local/lib/php/extensions/no-debug-non-zts-20230831/memcached.so: igbinary_unserialize: symbol not found)) in Unknown on line 0
app-1  |
app-1  | Warning: PHP Startup: Unable to load dynamic library 'redis' (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis (Error loading shared library /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis.so (Error relocating /usr/local/lib/php/extensions/no-debug-non-zts-20230831/redis.so: igbinary_serialize: symbol not found)) in Unknown on line 0
app-1  | 32.0.5.0) and downgrading is not supported. Are you sure you have pulled the newest image version?

Seems that the error message from #2509 is being jumbled into the error message from this bug...

Output of docker inspect for the current and older known good image:

mae@entrypoint /srv/nextcloud $ uname -a
Linux entrypoint.meow.solutions 6.12.65-0-virt #1-Alpine SMP PREEMPT_DYNAMIC 2026-01-14 11:57:55 aarch64 GNU/Linux
mae@entrypoint /srv/nextcloud $ docker inspect nextcloud:32.0.5-fpm-alpine --format '{{.Os}}/{{.Architecture}}'
linux/arm64
mae@entrypoint /srv/nextcloud $ docker inspect nextcloud:32.0.2-fpm-alpine --format '{{.Os}}/{{.Architecture}}'
linux/arm64

Feel free to let me know if you need anything else to help debug this issue.

[joshtrichards]

@mdartmann Your scenario looks similar to #2509. It usually raises if you've customized the PHP config or installation in some way or overwritten some PHP related mounts...

[mdartmann]

@joshtrichards thanks for the hint, changing the config bind-mount and only mounting custom config files into the php-fpm.d folder instead of having the entire /usr/local/etc folder as a volume fixed the issue on my end!