-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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]: Integrity issue "nextcloud-init-sync.lock" after updating docker container #2057
Comments
This seems a clue. Something appears to be up with the file permissions on your Docker mount for Check the file ownership and permissions of this file/folder and parents. I suspect this is a local environment/configuration issue. |
Thanks for your answer. I thought that, too. But the environment has not be changed from 27.0.1 to 27.0.2, the file had the same rights under 27.0.1. 27.0.1 has not shown this error. If I delete it and restart the container, it will recreated with the same rights. If I change the rights equivalent to the other ones, it makes also no difference. |
Please share your Docker Compose file. |
Hi Josh, of course:
I tried to keep it simple. But if there's mistake in my compose file, please fire away. By the way, I checked it with a new installation and it shows the same error. The strange thing is the file noted as extra file is created by the Nextcloud container. Reagrds |
By the way, after the last two image updates, the message still appears... |
Your file permissions indicate you're using ACLs: https://wiki.archlinux.org/title/Access_Control_Lists#Output_of_ls_command I'd review what the real underlying permissions are on that file on your Synology. The issue may also be related to You might be able to workaround it by adding this to the
But I can't promise that. I'm actually kind of surprised that the See:
The reason the integrity check is failing on it is because the check can't even open the file to do the check on it in your environment for some reason. |
Hi Josh, I try that... What's causing the creation of this file? Maybe the problem lies there and it is something in my installation, that i can have a look on. Thanks and regards |
The lock file gets created every time a container running this image starts up. It's used to make sure another process (or container with the same volume mounted) isn't already trying to install/upgrade the version of Nextcloud installed in Lines 135 to 136 in c496644
If I hadn't noticed the ACL permissions (that's what the |
The seccomp option changed nothing, I've just tried that. I restored my Nextcloud container from before the update to 27.0.2 to a parallel installation. With this 27.0.1 (27.0.1.2 according to config.php) the error disappears. The checks ends with "All checks passed." as expected. The ACL are the same. So a question would be, what has changed between this versions? When this file is only needed in case of other processes tried access this volume, is there an option to stop this? The volume is used by nothing other than the Nextloud container. |
Sorry for answering so late, I wanted to be sure it works over new updates. I tried again to set the rights of the file to www-data:www-data. This time it worked and the board is green again. The only difference: I checked it first in ssh with "occ integrity:check-core". That showed no error and in GUI no error is shown, too. It also survived two new docker images. So I think there's nothing more to do in this case... Thanks for your help! |
not working for me :( |
@pinkfloydFR See #2299 if you're seeing this with v30. |
Bug description
After updating docker container from 27.0.1 to 27.0.2 the integrity check failed:
Log entry:
Steps to reproduce
Expected behavior
Integrity check should show no error
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
Other
PHP engine version
PHP 8.2
Web server
Other
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 22.1 to 22.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
Running on Synology DSM 7.2 / Docker 20.10.23
The text was updated successfully, but these errors were encountered: