All: I am currently running:
Mattermost Version: 10.5.1 (preview edition)
Database Schema Version: 129
Build Number: 13392111033
Database: postgres
Hostname: ff091b6c5ba6
that I am able to run publicly with some cloudflare action, but obviously after we have tested, I want to move to our own self-hosted version.
I am currently running this through a docker containter off of a QNAP NAS and it is running inside of Container station on the QTS “OS”. What I tried to down, was get the latest update of team-edition but when i did the download and ran the container, it just shut off automatically. then when i just got the newer version of “preview”, which seems to be 11 (teams edition), it looks like it doesn’t attache the old DB to the new one, I assume bc treats it as a separate container and it doesn’t know all the users.
Is there a way to update to the newest teams on-prem edition that I self host in a new container and export my users/data/logins and such, so they don’t see any change, only my admins, as I would update the server to 11?
Where does your postgres database run? I can’t see a postgres container on the screenshot.
Are there more errors in the mattermost.log and what are your database settings looking like in config.json?
Edit: oh, and I hope you upgraded along the official upgrade path? v10.5.x is an extended support release (esr) and the next one is v10.11.x. You have to upgrade from esr to esr+1, not esr+2.
This local image is self-contained (i.e., it has an internal database and works out of the box). Dropping a container using this image removes data and configuration as expected. You can see the configuration settings documentation to learn more about customizing your trial deployment.
So if you didn’t configure a static storage for postgres (if possible, though), the new container won’t have access to the pre-existing data. That’s how containers work: no persistent data without proper configuration.
