Upgrade 10.13.3 to 10.16.3

Server
1

Hello OC community,

I’m running OC server 10.13.3 using docker-compose. As the latest version seems to be 10.16.3 I am wondering if I can upgrade directly by changing the version number in the env file to 10.16.3, or should I perform multiple upgrades sequentially. If I need to upgrade to 10.14 first and then 10.15, does it matter which point release I use – the last one available I’d guess?

Thanks for your attention.

1 Like
2

Hi frogola,

Good news — you can upgrade directly from 10.13.3 to 10.16.3. You don’t need to step through 10.14 and 10.15 one at a time.

The “don’t skip versions” rule in ownCloud only applies to major versions (e.g. you couldn’t jump from 9.x straight to 10.x without going
through the last 9.x release first). But 10.13, 10.14, 10.15 and 10.16 are all within major version 10, and the occ upgrade migrations are
cumulative — running it once from 10.13.3 will apply everything needed to land on 10.16.3. There’s no migration step in 10.14 or 10.15 that
has to run separately beforehand.

And yes, go straight to the latest point release (10.16.3). You don’t need to install 10.16.0/.1/.2 along the way.

Your instinct about changing the version in the .env file is right — that’s part of it, but editing .env alone won’t perform the upgrade.
Here’s the full docker-compose procedure:

  1. Back up your database and your data/config volumes first. Downgrading is not supported, so this backup is your only way back if something
    goes wrong.
  2. Enable maintenance mode and stop cron; block browser/proxy access to the container.
  3. Check your marketplace/third-party apps for 10.16 compatibility and disable any that aren’t ready:
    docker compose exec owncloud occ app:disable
  4. docker compose down --remove-orphans
  5. Edit the image version in your .env file — set OWNCLOUD_IMAGE=10.16.3 (the compose file references it as image:
    owncloud/server:${OWNCLOUD_IMAGE}).
  6. Start and run the upgrade:
    docker compose up -d
    docker compose exec owncloud occ upgrade
  7. (This can take anywhere from a few minutes to a few hours depending on the size of your install.)
  8. Reapply any manual changes you’d made to .htaccess / .user.ini.
  9. Turn maintenance mode off and re-enable access:
    docker compose exec owncloud occ maintenance:mode --off
    Then verify the version in the admin panel.

Two behavior changes in this range worth knowing about (not blockers, just heads-ups):

  • 10.16.0: the phar stream wrapper is now disabled globally, and subadmins can no longer add users to groups.
  • 10.15.3: the web updater was disabled — irrelevant for the docker upgrade path, which doesn’t use it.

Reference: the Upgrading and Manual Upgrade pages in the admin manual, plus the server changelog.

1 Like
3

Thanks much for the detailed reply DeepDiver1975. That’s indeed good news. I will schedule the upgrade for July and use your suggested procedure.

1 Like
4

Hi DeepDiver1975,

I just successfully upgraded my server from 10.13.3 to 10.16.3 using your procedure above. A couple of minor notes FYI: after editing the version number in .env and running docker-compose up -d, when I performed the exec owncloud occ upgrade it said could not perform upgrade while in maintenance mode. I turned maintenance mode off and retried and it said it was already upgraded. Which it was, I confirmed by connecting to the web interface and checking settings. So no need for the occ upgrade command.

1 Like