nextcloud / nextcloud/server

mimetype migrations warning after fresh Docker install

Open
#58,234 2 comments 0 reactions 1 assignee View on GitHub

@joshtrichards is already working on this.

Since Feb 10, 2026.

29-feedback 3. to review bug feature: install and update
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

After performing a fresh installation of Nextcloud using the official Docker image, I was presented with the following warning in the system overview:

One or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations

To resolve this, I had to manually run:
docker exec -itu www-data <container_name> ./occ maintenance:repair --include-expensive

Expected Behavior

A fresh installation of Nextcloud - especially via Docker, where users expect automation - should result in a fully working, clean state without requiring manual execution of (expensive) maintenance tasks, not immediately after first deployment.

Proposed Solution

Automatically perform necessary mimetype migrations during the initial setup phase (especially for new installs).

Impact
  • New users may be confused by warnings on a fresh install
  • Adds friction to automation, CI/CD, and reproducible deployment scenarios

Thanks for your attention, and for the work on maintaining the Docker image!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.