-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Image deletes everything when upgrade.exclude
does not exist
#1967
Comments
Ugh. Agreed. Sounds like you discovered this the hard way! We should add a check for the file's existence anywhere above here: Line 174 in bc963e0
I wonder if it's also worth making sure that, at a minimum, the six entries we ship in that list are simply always in there. In effect always including these ones: https://github.com/nextcloud/docker/blob/master/upgrade.exclude#L1-L6 ...by hard coding them in the |
upgrade.exclude
does not exist
Wait, are you sure you didn't just mount your old (source) "Nextcloud Instanz folder" underneath That's currently expected and documented behavior: https://github.com/nextcloud/docker#persistent-data Though it wasn't well documented until relatively recently in #1862 (and perhaps it could still use a better call out or it's own heading since it's easy to miss at the end of the Persistent Data section). |
Hi @joshtrichards , Sorry for my late response. Sounds on the one hand plausible, but then I must have seen an empty folder on my server, right? But I had a new nextcloud instanz under my old server folder with an empty data folder and a new config etc. I'll close this issue. I don't think it makes sense to further investigate this, as I can't give more infos (too long ago and I don't have the server anymore) and my first assumption turned out as wrong. Sorry for the inconvenience. |
Is:
Root-Cause:
Should:
The text was updated successfully, but these errors were encountered: