How to upgrade with compose and docker volumes

[wwe]

@oliv3r

So that doc lists as upgrade steps:

$ docker-compose pull
$ docker-compose up -d

I’m pretty sure I can’t mess that up much

that’s true but many people don’t read/follow the docs for this reason we always ask!

@oliv3r

    cap_add:
      - setgid
      - setuid
    cap_drop:
      - all

I was curious if cap_add/cap_drop order might be a problem but seems to be OK according to Docker-Compose: order of cap_drop and cap_add? - #3 by thediveo - Compose - Docker Community Forums this is the most noticeable difference from default - check if it works without this directive in the future

@oliv3r

We should chown everything to www-data. Obviously, while checking this again right now, I noticed that maybe I was a bit to overzealous with my chowning. I changed ownership of /var/www/html instead of just config and custom_apps. So i’ll switch the standard nextcloud files to root:root! It makes sense, nobody should be able to edit those files …

I would expect root can rsync files of another user but not other way round. As you can see in my guide Nextcloud docker-compose setup with notify_push (2024) apps, config and data are owned by the limited container user (which IMHO translates to www-data by default)

@oliv3r

split out config (and custom apps, but I’m sure that’s already possibly)

you are right it is possible (see the guide above) or container docs > additional volumes