Post mattermost-docker migration minor issue with docker container health

Hey Mattermost team, great work!

I was on mattermost-docker up until now. I had used the early version of the upgrade script to get my postgres instance onto version 13.2 and all has been well.

I saw the movement towards this repo as the main docker repo and so I wanted to migrate over. I upgraded my mattermost-docker instance up to version 5.39, the latest, and that started up just fine.

Then rysnc'd my volumes directory from mattermost-docker to this repos volumes directory. I set up tthe .env witth all the old settings for the postgres username, database name, and password. The postgres database started okay, but the new mattermost docker was having errors about my postgres user not being able to authenticate of course causing mattermost to not start up.

I noticed a small discrepancy in the way the database directories were set between the 2 repos.

The new docker repo (this one) had the path being passed into the container like this:
./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data

However, with the upgrade script I used from the other repo on the mass thread about the postgres migrations has it set like this:
./volumes/db/13/data:/var/lib/postgresql/data

So, I ended up just updating my .env file from this new repo to have this instead:
POSTGRES_DATA_PATH=./volumes/db/13/data

So now the containers both start up, and it appears to be working just fine. However, the docker container for mattermost reports that it's state is "unhealthy".

Admittedly postgres is not my strong suite when it comes to databases. Should I do it differently somehow? Maybe copy the data from ./volumes/db/13/data to ./volumes/db/var/lib/postgresql/data?

Again, everything is working and I can't tell why the container reports as unhealthy, thus why I call it a minor issue. I'm just concerned there might be underlying issues I'm not seeing yet.

Any suggestions, concerns, thoughts?

Start with the .env setting POSTGRES_DATA_PATH and compare the two volume paths described: ./volumes/db/13/data and ./volumes/db/var/lib/postgresql/data. Check the Mattermost container's reported health status alongside the PostgreSQL container after migration; done means the correct data path is established and the health status is explained or corrected.