-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] issue with update 27 #324
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
With the exception of the files listed under To remove the files under the core section, you will need to recreate the container (not just restart). If you're using docker compose, you can run This issue seems to be happening to everyone, but the files listed depend on the apps installed in each individual nextcloud instance, so I haven't found a way to automate cleanup yet. |
I'm also having the same issue, running in a docker on unraid. Should I expect a future fix patch or am I required to take action to solve the issue? |
same here, just updated on unraid and now im seeing this :( |
#325 should fix the integrity check issue I've tested this on my personal instance, and a few other team members plan to test as well, but additional confirmations would be great. We'll merge these changes and release a stable build as soon as we have enough confirmations. |
That’s what I did. Removed photo. Reup. Worked. And did that for all the apps |
does this work on unraid? can i safely use nextcloud even if i don't fix this error? |
I had this issue yesterday and reverted to a backup. I was wondering if my issue was not to upgrade from a docker image defining nextcloud 26 to one on nextcloud 27 without upgrading first nextcloud. I reverted the installation to the 26.0.2-ls248 image, and a 20.0.2 installation on my mount. I guess this is the safest bet here. |
yes
yes |
If you have apps that require specific compatibility, your best bet is to pin your docker image to a specific version that is compatible with all your apps, and if that version is below 27 you should manually update the install files to that version of nextcloud. If you delete |
Didn't work for me unfortunately. This is what I did:
I also did it twice (second time just restarting the container instead of changing the image tag), as I wasn't sure if I forgot creating the This is the output (seems to only be about not-preinstalled apps): Integrity check output (From "https://cloud.mydomain.com/settings/integrity/failed")Technical informationThe following list covers which files have failed the integrity check. Please read Results
Raw output
|
@koelle25 can you try re-running |
It's work, thanks. my env: my flow:
|
Next question: Can i switch image back to |
Yes |
I have the same problem. Then I did hit Rescan and the error it's fixed. This is part of the logs after the change:
|
Did the same, switched back to
Tested and now everything appears to work fine, so I switched back the image to |
I'm running the container on my server using Unraid and after performing the fix listed in the above the error went away, but now I can no longer run the OCC command. Running: Results in: |
OK had and issue in unraid docker. I guess the upgrade is not as automatic as letting the container upgrade. I went back to the 26 major version (lscr.io/linuxserver/nextcloud:version-26.0.2). Dont mess with the web interface upgrade always getting errors. Open a console and run "occ upgrade". Then goto next version and run again. |
|
The process you did is correct to get current. Once you're running Nextcloud 27 you can use the latest image and all future updates should be automatic when you update the container image. |
This should be resolved now with the new image release. |
Thanks. It work for unraid Docker... |
it say "No such file or directory" |
Step by Step
if the docker disappears for some reason, you specified the repository incorrectly. The Docker can then disappear. But don't worry, just go to ADD Container at the bottom of the docker and select Nextcloud and adjust the repository again. Good luck! |
The changes to fix the integrity check have been merged. The best option now is to run the latest image
That should make the init script cleanup the files, and then you can trigger a rescan in the nextcloud admin status page by clicking rescan. |
Worked! |
Thanks @swiss01 , now it worked for me too. I also already changed back to the release tag ( |
WORKS flawlessly |
EDIT: Nevermind. It works. |
Same here, in the end it worked, dont be irritated if the failure is still present after the first edit, in my case it was gone after going back to the latest one. |
Hi All! Got here the same error and was hoping i could you this fix to.. but i'm running a newer version atm.. 27.0.1.2 Can't start Nextcloud because the version of the data (27.0.1.2) is higher than the docker image version (27.0.0.8) and downgrading is not supported. Are you sure you have pulled the newest image version? Is there any way to fix this ? |
Update: Cheated the system a little... Edited the config.php file to bypass this error, bring up the new container and is worked! did a semi manuel update by browser, switches back to the common version and all was back on track! Love it! Thanks! |
From this point, don't update nextcloud via the web. Just update the container image when we release new versions (usually within an hour or so after nextcloud releases a new version). |
Thanks for the reply! |
That sounds like an issue how you have set up your compose or file permissions. Updating via |
Thanks! The "-d" is causing the permission denied error from docker ? |
no, the |
What could be the cause of the error? Pid user rights? |
Could you post the full log here from when you run the command? |
Something simple as: sudo docker stop nextcloud compose config: version: "2.1" Could it be the PUID PGID ? Root hass 0 and Common user has the 1000 ? |
That seems like your user isn't in the docker group. You could add your user to the docker group or run the command with sudo. |
Is there an existing issue for this?
Current Behavior
After update I have inside administration settings
Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the [documentation ↗]
The files incriminated:
`Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
Raw output
Array
(
[core] => Array
(
[EXTRA_FILE] => Array
(
[dist/files_trashbin-files_trashbin.js] => Array
(
[expected] =>
[current] => 24e537aff151f18ae18af31152bcfd7de9c96f0f6fdcca4c1ad975ece80bb35a2ab7d51c257af6a9762728d7688c9ba37a5359a950eb1e9f401d4b9d875d92b2
)
)`
Expected Behavior
Green flag
Steps To Reproduce
Update to the new container nextcloud 27
Environment
CPU architecture
x86-64
Docker creation
--- version: "2.1" services: nextcloud: image: lscr.io/linuxserver/nextcloud:latest container_name: nextcloud environment: - PUID=1000 - PGID=1000 - TZ=Europe/Paris volumes: - ./config:/config - ./data:/data - /mnt/NAS/:/opt/NAS ports: - 5010:80 - 5011:443 depends_on: - mariadb restart: unless-stopped mariadb: image: mariadb:latest container_name: nextcloud_mariadb environment: - PUID=1000 - PGID=1000 - MYSQL_ROOT_PASSWORD=xxxxxxxxxxxxxxxxx - TZ=Europe/Paris - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_PASSWORD=xxxxxxxxxxxxxxxxx volumes: - ./mariadb:/var/lib/mysql restart: unless-stopped
Container logs
The text was updated successfully, but these errors were encountered: