-
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
Massive problems when updating to 20.0.7 #1404
Comments
By the way: it's running on arm32v7 and building the image with alpine 3.12 fixed the problem for me. |
The reason is https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.13.0#time64_requirements. |
The same happens when updating 19.0.7 to 19.0.8. Alpine changed from 3.12.3 to alpine 3.13 in this minor update... |
The description in the link above solved the problem for me. I didn't close the issue because I'm interested if there will be some discussion about the major alpine update with a minor nextcloud update. |
Do you mean rebuilding musl 1.2? How did you do that? IMHO, I agree that one shouldn't expect such massive changes with minor updates. |
No I mean |
My fix to this was to just update |
Ok, so you don't use the official debian package, right? |
@haho16 Thanks a lot! I added the buster-backports repo, installed @escoand Not sure how you are running NC. I use the official Docker NC image with docker-compose (based on the example files in this repo). |
I'm using the pre-build |
The latest Redis release fixed some major issues with 32bit systems: https://github.com/redis/redis/releases/tag/6.2.0 |
So it's safe to say Alpine 3.13 and older Docker versions are causing massive problems for a lot of people running on RPI4. I didn't want to run Nextcloud with the seccomp sacrifices, so downgraded Nextcloud following the hints from @escoand - However my Docker-Compose calls for 'redis:alpine' and of course they've also updated to Alpine 3.13 as a base image, so that was crashing out immediately too. I then ended up in a bad place with version mismatches between Nextcloud and the MariaDB database I also use. Much confusion. Eventually I decided to upgrade libseccomp2, but also to install Docker 20.10 using the Debian Bullseye repo. It is essentially just an upstream of Debian Buster, and has a newer version of Docker which works just fine with Alpine 3.13. I documented what I did here: |
Another option is to install Docker from its own repository. I would recommend that rather than using the repo for the next major Debian release. |
Closing as duplicate of #1589 |
I've updated my fpm-alpine containers from 20.0.6 to 20.0.7 and now have massive problems including various connection errors to redis and mariadb.
After downgrading to 20.0.6 (and changing
/var/www/html/version.php
) everything is working again.This is reproducable.
nextcloud.log
has some weird date entries and stating it's still 20.0.6:My
docker-compose.yaml
:As with downgrading just the image (but not the volumes with the php files) it seems to be problem of the image itself.
The text was updated successfully, but these errors were encountered: