Docker upgrade NC from 14 to 15

rvalle · December 17, 2018, 7:19pm

hi!

I run NC using Docker Compose.

I am currently using “latest” as version for the NC container.

I pulled the new NC version hoping that everything would continue to work without any other particular update procedure. is that a reasonable expectation?

after pulling my NC is not working… its complaining about db credentials.

any idea what is going on?

Reiner_Nippes · December 17, 2018, 8:45pm

where was/is the config.php? inside the container? or on the host filesystem?

rvalle · December 18, 2018, 9:34am

it is inside the container.

I can see that there is a custom.config.php with smtp settings only that’s outside of it.

php fails related to DB connection for user “oc_admin” however my POSTGRES_USER environment variable is “postgress”

looks like it is ignoring env vars, perhaps using defaults?

Reiner_Nippes · December 18, 2018, 9:55am

that’s the wrong place. nothing that is changed during operation is allowed inside a container.
if you don’t put /var/www/html in a volume all your changes to your nextcloud will be gone with that container.

example:

github.com

nextcloud/docker/blob/master/.examples/docker-compose/with-nginx-proxy/postgres/fpm/docker-compose.yml#L16


      
            restart: always
            volumes:
              - db:/var/lib/postgresql/data:Z
            env_file:
              - db.env
          
          redis:
            image: redis:alpine
            restart: always
          
          app:
            image: nextcloud:fpm-alpine
            restart: always
            volumes:
              - nextcloud:/var/www/html:z
            environment:
              - POSTGRES_HOST=db
              - REDIS_HOST=redis
            env_file:
              - db.env
            depends_on:

that indicates (to me) that in the new container the initial setup didn’t run. and you have a strange state. you have no config.php but you have a postgres database. so the initial setup fails because it can’t create the database. as far as i remember that is not cover by the script.

rvalle · December 18, 2018, 12:28pm

yes, I have a volume for /var/www/html
then i am mounting a custom.config.php with mail settings only.
everything else is provided by the pulled image.

I think I have followed the examples /documentation properly

Reiner_Nippes · December 18, 2018, 12:57pm

so do you have still the old config.php? what happens if you put this one in place (var/www/html/config/config.php)?

rvalle · December 18, 2018, 8:16pm

I see.

NC documentation says that the data volume is /var/www/html

However the image-dependent config.php is actually stored within the data volume in /var/www/html/config.

This basically means that pulling an update is never going to work unless you update your data volume with files distributed in the new image.

do you think this is what is happening?

but it is strange. I read the documentation again and this is the way it is supposed to be. an update process should have been triggered.

and I can see the following line in config.php
‘version’ => ‘14.0.4.2’,

custom.config.php is mounted as:
custom.config.php:/var/www/html/config/custom.config.php:ro

so, I think it should not interfere with

Reiner_Nippes · December 19, 2018, 9:46am

a script is doing this for you. when you look at the entrypoint.sh script of the nc docker image you’ll see that the update is done in that script (if needed). the script copies the nextcloud php files from /usr/src/nextcloud/ to /var/www/html/ with an rsync command.

https://github.com/nextcloud/docker/blob/master/15.0/fpm-alpine/entrypoint.sh#L47

in the file upgrade.exclude you can see what is not synced because these are user created/modified files. and therefore should not be over written. in line 49 the script checks if the directories exists and creates them if needed.

https://github.com/nextcloud/docker/blob/master/15.0/fpm-alpine/upgrade.exclude

that looks bad. if config.php isn’t writeable by nextcloud you can’t do any changes to your nextcloud (that are store in the config.php) that includes update to another version.

hope that helps you find out the right configuration.

rvalle · December 28, 2018, 11:20pm

I am not getting it to work
I tried to stop mounting any custom settings and trigger the update script again, by modifying the versions.php and leaving it as 14.0.0

still keeps trying to connect to the database with a default username ignoring the environment variable. Unfortunately I have very little time to put on this.

I find very troubling that my data volume includes, basically, the whole nextcloud PHP code. this is not the idea behind the volumes. Being able to replace the container image while keeping the data is a key benefit of docker.

I am going to wipe the data volume and get a fresh install, as I have no data of value, I am mostly testing the viability of replacing my Synology by Nextcloud.

I will open a but with NextCloud.

thanks for your help!