On upgrade: Warning: /var/www/html/config/….config.php differs from the latest version of this image at /usr/src/nextcloud/config/….config.php
#2266
Comments
|
Same here, and upgrade scripts to 29.0.4 will not work. |
|
Sorry, my mistake. Not changig to the latest image tag... Now upgrade scripts are working but warnings still appears |
It's referencing your configs stored on persistent storage, not something in the image. Docs w/ explanation: https://github.com/nextcloud/docker?tab=readme-ov-file#auto-configuration-and-nextcloud-updates Additional references: |
|
Ah, would be great if the error message could link to the description or so or otherwise make it clear, that one can copy the files from the target to the source to fix this. As I've never modified the multiple files, and I actually also, as aah… as far as I see now, I never even had copied the original files. I still have only one $ podman-compose exec nc sh
# cd /var/www/html/config
# ls -la
total 12
drwxrwxr-x. 1 www-data www-data 100 Jan 24 2022 .
drwxr-xr-x. 1 www-data www-data 554 Jul 25 09:23 ..
-rw-r-----. 1 www-data www-data 2787 Jul 25 09:24 config.php
-rw-r--r--. 1 www-data www-data 319 Feb 29 11:56 mimetypealiases.json
-rw-r--r--. 1 www-data www-data 439 Feb 29 11:56 mimetypemapping.jsonIs there any good upgrade migration/path/recommendation on how to split the file, apparently? Also the JSON files are apparently created by Nextcloud or by me for some extension (OnlyOffice or Nextcloud Office maybe?): # cat mimetypealiases.json
{
"": "x-office/document",
"application/vnd.openxmlformats-officedocument.wordprocessingml.document.docxf": "x-office/document",
"application/vnd.openxmlformats-officedocument.wordprocessingml.document.oform": "x-office/document",
"application/x-ownpad": "pad",
"application/x-ownpad-calc": "calc"
}# cat mimetypemapping.json
{
"pad": [
"application/x-ownpad"
],
"calc": [
"application/x-ownpad-calc"
],
"maps": [
"application/x-nextcloud-maps"
],
"noindex": [
"application/x-nextcloud-noindex"
],
"nomedia": [
"application/x-nextcloud-nomedia"
],
"noimage": [
"application/x-nextcloud-noimage"
],
"notrack": [
"application/x-nextcloud-maps-notrack"
] |
I think we did have a link in the warning at one point during development but removed it to streamline things. Oops. 🤣
You shouldn't have to split anything. Basically just add the additional files and leave your existing
Those can stay in place. Essentially anything you have is fine. The additional files are for supporting all the documented Docker auto-configuration stuff (mostly) and a few other requirements like disabling the web updater (which is never to be used with the Docker image). |
I am unsure what streamlining would mean in that context and how removing such a link helps there, but if you want then well… re-add it? Also the Readme says:
This is not true anymore, is it? The config PHP's always read the env via |
joshtrichards
changed the title
Warning: /var/www/html/config/….config.php differs from the latest version of this image at /usr/src/nextcloud/config/….config.php
|
The exact same thing happened to me. I run on K8s and upgraded a few months back via helm and major release. Step by step. Which is weird. However, I replaced them all on the remote server with the version from the image and it didn't help. Error: And it doesn't load. |
|
Since I have a backup, but only a one-day backup, I deleted the files mentioned above and hoped that Nextcloud would handle it somehow. Unfortunately, it didn't. So neither overwriting the files on the server nor deleting them helped. Worse, however, is that I'm losing track of where it actually sees the files. Somehow it doesn't make sense to me: And beware, this is on the server: In helm chart values there is only this and nothing has changed |
|
How do I revert to an older working version? |
You're getting 500 errors - something else is going on here for you. The warnings about older config files would not cause this from just a simple image update. To figure out why you're getting those 500 errors you'd need to check your |
As for nextcloud#2266 and the re-appearing message IMHO, it is quite convenient to have a command to copy here if you just have not changed any config files… Signed-off-by: rugk <[email protected]>
As for #2266 and the re-appearing message IMHO, it is quite convenient to have a command to copy here if you just have not changed any config files… Signed-off-by: rugk <[email protected]>
When upgrading from Nextcloud 28 to Nextcloud 29 I got these warnings. As they relate to stuff inside of the image and no plugins or configs, which are thought to be adjusted, I thought this might be wrong (or it would not be a warning, would it?):
Compose file (with
podman-compose):Startup command for testing is:
podman-compose -p nextcloud down&&podman-compose --in-pod=0 -p nextcloud up -dConfig
{ "system": { "memcache.local": "\\OC\\Memcache\\Redis", "apps_paths": [ { "path": "\/var\/www\/html\/apps", "url": "\/apps", "writable": false }, { "path": "\/var\/www\/html\/custom_apps", "url": "\/custom_apps", "writable": true } ], # ... "app_install_overwrite": [ "ransomware_protection", "bookmarks_fulltextsearch", "news" ], "maintenance_window_start": 1 } }Images used
System
Fedora CoreOS 40
Expected result
IMHO no warnings about such a file should be issued if I am using an official container image. In such an image, I expect all files to pass the validity check for obvious reasons… this warning is thus somewhat disturbing.
Current result
Warning, see above
The text was updated successfully, but these errors were encountered: