Closed vitoyucepi closed 4 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
https://github.com/linuxserver/docker-nextcloud/issues/324#issuecomment-1629767386 should fix the issue
Hi @nemchik, It seems that the suggested commands don't fix the problem.
docker compose exec app touch /config/www/nextcloud/config/needs_migration
Restart container.
This should be resolved after the next time a new version is released (the container does some cleanup when it installs new versions) or you can manually remove the files. You may also try recreating the container (not just restarting) and this could also resolve the issue now that you've done the steps above.
Yes, I can confirm that upgrading from 26.0.2 -> 27.1.3 -> 27.1.4 fixes the problem. In my case, the integrity problem will be solved after upgrading to 27.1.5.
If you don't have a better solution, feel free to close the issue with won't fix status.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Ping @nemchik.
Can you try running docker compose down app
(in your case the container for nextcloud is names app, according to your compose) then bring it back up? This should stop and remove the container and then recreate it. It should ensure there are no leftover files from a prior install/upgrade/migration on the inside of the container. Your persistent files should still exist in /config
and /data
. All of the extra files mentioned look to be core and lib files, which normally exist inside the container, and if you recreate the container they shouldn't be there anymore.
You can check for the files by opening a terminal into the container, ex: docker exec -it app bash
and then listing files/folders, ex: ls -lah /app/www/public/core
or ls -lah /app/www/public/lib
(note that there are a handful of folders listed in your extra files, you can check or all of them if you'd like). None of the extra files should exist if you've recreated the container (or pulled a new image to upgrade versions). Those paths are all internal to the container and should not persist through a recreate.
Thanks @nemchik, Yes, stopping and removing the container helps. This also happens when you upgrade from one version to another.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Hey @nemchik, Are we happy with the current level of the issue mitigation?
Yes. I haven't seen many cases where updating the container image doesn't fix the issue.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
When upgrading from 26.0.2 to 27.1.4 I get the same result as described in #324. Some of the files in the nextcloud installation are marked as EXTRA_FILE.
Expected Behavior
No integrity check warnings.
Steps To Reproduce
compose.yaml
Start compose project using
docker compose up
.Go to http://localhost:30443 and finish the initialization process.
Run
docker compose exec app occ integrity:check-core
to verify that everything is fine.Stop compose project.
Change
linuxserver/nextcloud
image tag from26.0.2
to27.1.4
.
```yaml services: app: image: linuxserver/nextcloud:27.1.4 restart: always environment: TZ: UTC volumes: - app_data:/data - app_config:/config ports: - 30443:443 db: image: postgres:16.1-alpine restart: always volumes: - db_data:/var/lib/postgresql/data environment: TZ: UTC POSTGRES_DB: nextcloud POSTGRES_USER: nextcloud POSTGRES_PASSWORD: nextcloud volumes: db_data: {} app_config: {} app_data: {} ```compose.yaml
Start compose project and wait until migration ends.
Remove old nginx configs.
docker compose exec app rm /config/nginx/ssl.conf /config/nginx/site-confs/default.conf
.Restart compose project.
Run
docker compose exec app occ integrity:check-core
to get the verification error.Environment
CPU architecture
x86-64
Docker creation
docker compose up
Container logs
Init log
``` [migrations] started [migrations] 01-nginx-site-confs-default: executing... [migrations] 01-nginx-site-confs-default: succeeded [migrations] done usermod: no changes ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 911 User GID: 911 ─────────────────────────────────────── Setting resolver to 127.0.0.11 Setting worker_processes to 6 generating self-signed keys in /config/keys, you can replace these with your own keys if required .+......+......+.....+...+............+++++++++++++++++++++++++++++++++++++++*....+.+++++++++++++++++++++++++++++++++++++++*..+......+..+.........+...+.......+...+........+...+..........++++++ ......+...............+.+++++++++++++++++++++++++++++++++++++++*.+.....+++++++++++++++++++++++++++++++++++++++*.+.....+......+....+.....+.......+..+...+...+....+.....+......+....+..+.+...+.....+...........................+...+............+...+....+...+..+............+...+.......+...........+....+.........+...........+..........+.........+..............+.+.....+....+.....+............+....+...........+..........+...+.................+.+.....+.........+.........+.+...+.....+.+..+...+...............+.......+...+............+.....+...+......+.+........+......+.+..............+....+..+..........+.....+............+.+..............+.+.....+....+............+...........+...+......+...+.+......+...+...........+.+..................+...+...+...........+.+..............+.+....................+...++++++ ----- # do daily/weekly/monthly maintenance # min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly # nextcloud cron */5 * * * * s6-setuidgid abc php -f /config/www/nextcloud/cron.php cp: not replacing '/config/crontabs/root' [custom-init] No custom files found, skipping... [ls.io-init] done. ```Upgrade log
``` [migrations] started [migrations] 01-nginx-site-confs-default: skipped [migrations] 02-default-location: executing... updating root in /config/nginx/site-confs/default.conf [migrations] 02-default-location: succeeded [migrations] done usermod: no changes ─────────────────────────────────────── ██╗ ███████╗██╗ ██████╗ ██║ ██╔════╝██║██╔═══██╗ ██║ ███████╗██║██║ ██║ ██║ ╚════██║██║██║ ██║ ███████╗███████║██║╚██████╔╝ ╚══════╝╚══════╝╚═╝ ╚═════╝ Brought to you by linuxserver.io ─────────────────────────────────────── To support LSIO projects visit: https://www.linuxserver.io/donate/ ─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 911 User GID: 911 ─────────────────────────────────────── using keys found in /config/keys Migrating legacy install (this can take a while) ...) Initializing nextcloud 27.1.4.1 (this can take a while) ... Upgrading nextcloud from 26.0.2.1 ... Setting permissions Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Setting log level to debug Turned on maintenance mode Updating database schema Updated database Updating