ownCloud 10.8.0.4 runs in a docker container, update channel = stable.
in all versions before i got an indication that a new version is available, BUT NOT NOW.
the updater says that the latest version is installed.
what needs to be triggered, that the updater recognizes a new available version?
And you run docker-compose pull and then docker-compose up -d to update it.
You should NEVER click the updater button within ownCloud, it should actually be disabled, because a properly built and configured container would lose any of the application changes on a restart.
@eneubauer:
my owncloud docker instance was previously deployed by “docker pull owncloud”, which used a pretty old version of 10.0.10. i updated this old version by “update” with the webfrontend, which worked until 10.9. now i’m stuck as the php version is too old.
i understand that “docker pull owncloud” is now outdated and it should be “docker pull owncloud/server”.
my question is: should i update with docker-comose.yml or can i still use the “docker pull owncloud/server” !?
what is the difference and/or what is the recommended way for the future?
Unfortunately these old containers were before my time I wasn’t even aware until you mentioned it, that it was ever different from the current way.
I can only say, that you need a test system were you can try out an upgrade process. I won’t have time to try figure that out. I don’t even know whether I would still be able to try, as I don’t know where to get that container.
But some pointers what you should look out for:
volumes and their mountpoints might be different between container images
make sure you have a backup and you know how to restore it
If you have specific error messages when testing your upgrade please don’t hesitate to post here for help.