Upgrading from installation dated Feb 2019

I installed Kobo on our own server back in February 2019 using instructions that you used to host as install-kobotoolbox-on-your-own-servers. Unfortunately that page no longer exists. I have a copy of those instructions here, but clearly time has moved on.

I’m looking at performing a major upgrade to your current release version. I’ve been carefully reading GitHub - kobotoolbox/kobo-install: A command-line installer for setting up and running KoBoToolbox on a remote server or local computer, using kobo-docker., and I’m aware I need to perform the manual upgrade described there too. I’ve also seen anoher post about this age of upgrade.

All good so far. However, on my Linux-based server I have a number of docker containers installed by the original installation script. I can “get by” with Docker, but I’m not terribly familiar with it.

In my top-level kobo-docker directory there’s a .git directory. If I head in there and run git branch I get told I’m on master. That seems to pre-date your instructions to use stable or some other specific branch

root:~/kobo-docker/.git# cat config
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = https://github.com/kobotoolbox/kobo-docker
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
        remote = origin
        merge = refs/heads/master

However, if I checkout git checkout stable, will that update all the Docker images, or are they now obsolete?

root:~/kobo-docker/.git# mount -t overlay
overlay on /usr/local/app/docker/3a8f...0f43/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/DRQI...
overlay on /usr/local/app/docker/01d3...3c51/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/4HTD...
overlay on /usr/local/app/docker/96cf...ce57/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/XXVC...
overlay on /usr/local/app/docker/1014...5e4d/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/IK7U...
overlay on /usr/local/app/docker/1b3a...a350/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/DYF4...
overlay on /usr/local/app/docker/b4d8...1a6f/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/5CS4...
overlay on /usr/local/app/docker/3b8d...44fb/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/MMGO...
overlay on /usr/local/app/docker/6801...331c/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/UVBW...
overlay on /usr/local/app/docker/5ef2...ed69/mergedtype overlay (rw,relatime,lowerdir=/usr/local/app/docker/overlay2/l/RILU...

I’m starting to wonder if building out a new Linux-based server would be my best bet. If I do this, though, I’d want to copy across the existing set of usernames and passwords. We have about fifty of these active and, as many of the users don’t speak English, issuing new passwords and getting them to update their phones will be a non-trivial process.

Many thanks