4censord
4censord
So this seems to be related to the `FROM node:10-alpine` statement. If this is changed to a later version (tested with `FROM node:15-alpine`) it works.
Hey, what would be needed to get this merged? Also, is it possible to backport this change to the last 3 versions, so 25, 26 and 27?
I'll take a look at resolving the conflicts. > With this chart there is no backporting, you just overrride nextcloud.tag with your desired version. Ok
The conflicts are solvable by simply rebasing onto the main branch. @remram44 can you rebase, please? Or if you'd be fine with that, i could open a new PR with...
> And I will be left with the pod crashlooping forever until I manually fix it using `occ` commands. How exactly are you fixing this? I am left on 25.0.1...
@budimanjojo Then i seem to have a different issue, that does not work for me. I have to roll back a backup after attempting an upgrade.
@provokateurin Would you mind taking a look at this once it's convenient? IMO its ready.
IIRK the upgrade env var is used for triggering the Nextcloud images upgrade mechanism. But because this PR completely supersedes the internal `upgrade on startup` stuff by running the upgrades...
> Then we have a race condition between the two containers and depending on which one gets to work first the upgrade is killed by the probes or not. No,...