Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
I’m using the docker images at https://hub.docker.com/\_/nextcloud , specifically fpm-alpine, though the issue I’ve found affects all of them.
I see that the latest versions of all the images indicate they were built today and from the latest commit ( https://github.com/nextcloud/docker/commit/32ff0009669d4a63671e6dff0bb137357b9c0a2d ) which bumped the Nextcloud version to 32.0.2. However, when actually inspecting the images, they all still contain Nextcloud 32.0.1, as seen for example here (https://hub.docker.com/layers/library/nextcloud/fpm-alpine/images/sha256-8ac30079fce9bcfc6371a81239251f18ada30e685e29834740fd12acd5f26745).
Is this just routine delay in how images are built/tagged on DockerHub? What’s confusing me is the seeming contradiction between the commit DockerHub claims the image is built from, and the actual contents of the image.