Ok, I’ve downloaded docker-compose version 2.17. I’ve also changed the version of the docker-compose yaml’s to version 3 and I don’t receive “Failed to ping DB” anymore however, I’ve found a new way to fail now because the UI won’t load when I navigate to the 10.200.x.x:8065 address.
Looking at the logs there are a few errors but none that I think are relevant right now. For instance, there is a fail to connect to the SMTP error but I’m not going to use SMTP. I’ve attached a shot of the error logs from the mattermost.log file:
Good, this looks better now, but your database does look corrupt, it is not able to read the admins from it and it’s failing to read the pluginkeyvaluestore tables, so something must still be wrong with the database access.
Since this is a new install, can you please (with the new docker-compose version in place) just start over? Wipe your current docker folder (it should not contain any data anyways, since you’ve just started) and start over new following the documentation. If you already have a reverse proxy or do not want to use SSL (which you should, but just saying) you can stop right after step 3.
After a long hard look, I discovered gitlab-ce comes with Mattermost. With that being said I don’t have the need for a stand alone container of MM. I’m not sure why this issue existed on the AWS EC2 instance of Ubuntu that I tried to install it on but after I switched gears the gitlab image is working much better for me.
