March 14, 20251 yr I am using the nextcloud aio docker container (nextcloud-aio-mastercontainer). The mastercontainer spawns several other containers nextcloud-aio-mastercontainer such as the database, apache, etc. Exactly these "spawned containers" (which are created by the mastercontainer and not by myself) are always at this "apply update" step, but obviously trying to update those leads to an error. How to deal with it? There seems no chance to get rid of this update message.
March 14, 20251 yr Stay cool. The idea is to update the master container (once an update is available), then start the gui for it (need to logon to "normal" nextcloud and enter admin settings, there is a button to start it) and finally THERE you will find the option to update the slave containers... (Yeah if this sounds complicated, you have understood it). AIO is a p@*n in the @ss and should be elmimimated as soon as you can. (BTW, the option to update will only be available AFTER a complete backup through AIO...)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.