-
-
Notifications
You must be signed in to change notification settings - Fork 129
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] EXTRA_FILE
when upgrading 26.0.2 to 27.1.4
#385
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
EXTRA_FILE
when upgrading *26.0.2* to *27.1.4*
EXTRA_FILE
when upgrading *26.0.2* to *27.1.4*EXTRA_FILE
when upgrading 26.0.2 to 27.1.4
#324 (comment) should fix the issue |
Hi @nemchik,
Verification log
|
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. 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 You can check for the files by opening a terminal into the container, ex: |
Thanks @nemchik, |
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, |
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
.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
Upgrade log
The text was updated successfully, but these errors were encountered: