Some assistance getting this up and running about mattermost-docker HOT 4 CLOSED

Thank you for the reporting!

For the SSL certificate stuff, I followed the first part of this, in terms of generating a *.key and *.crt file ... and then renamed these as key-no-password.pem (putting it in /web/cert/private/) and cert.pem (putting in /web/cert/) respectively.
Is this the right approach in order to then work with your 'web' container here?

It is correct if you didn't input passphrase while creating the key file.

Running up postgres
For the 'volumes' references back on the host machine ...

• ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
  Do these need any special permissioning?

Yes but Docker will give the correct permission to the directory automatically.

I have some questions to understand your problem.

1. What happens when you try to acces your mattermost with your web browser? Connection refused or 502 gateway error?
2. Does docker ps show that db, app and web is up?
3. Are you sure that you accessed it via https? e.g. https://host.domain

from mattermost-docker.

@npcode
I feel a bit foolish ... I was trying http:\\localhost instead of https:\\ as you point out in 3 above.

Even though I have created the self-signed certificate, is it normal that I still get all these warnings about https://localhost ... when accessing via a web-browser?

I did notice some slight problems in getting all three containers up and running simultaneously. It seems if the database is not fast enough to offer a connection, then the other containers won't start. I see in the log output from the db container, that it refers to a previous instance not being closed properly ... this shows up even if I stop and remove earlier containers ... perhaps it has something to do with 'volumes' connection back to the host keeping remnants of the old database ... and perhaps that should be cleared as part of a clean-up process.

~/Development/Tools/misc/mattermost-docker$ docker-compose up -d
Creating mattermostdocker_db_1
Creating mattermostdocker_app_1
Creating mattermostdocker_web_1
ERROR: Cannot start container 2dffebe07b34f45c1c9baa9bbf5c9440f8600c15d20e9b50efac9c82942de83e: Cannot link to a non running container: /mattermostdocker_app_1 AS /mattermostdocker_web_1/platform

If I had another existing container running postgres (for another system), it's probably not advisable to have another exposing posrt 5432 too. Therefore, it perhaps makes sense to extend the existing one. Do you know if it's possible for me to run only the database creation step ... and somehow run this make_db.sh as a command within the docker-compose.yml?

ADD make_db.sh /docker-entrypoint-initdb.d/

I presume it's OK to redirect port 80 in the app to a different port on the host, without impacting the app?

Thanks again for your quick response.

from mattermost-docker.

I feel a bit foolish ... I was trying http:\localhost instead of https:\ as you point out in 3 above.

Sorry, I was too lazy to make the web server redirects 'http' to 'https' automatically. :)

Even though I have created the self-signed certificate, is it normal that I still get all these warnings about https://localhost ... when accessing via a web-browser?

Yes, you will get the warning because you are using self-signed certificate which your browser doesn't trust. You can try let's encrypt to get a trusted certificate.

If I had another existing container running postgres (for another system), it's probably not advisable to have another exposing posrt 5432 too. Therefore, it perhaps makes sense to extend the existing one. Do you know if it's possible for me to run only the database creation step ... and somehow run this make_db.sh as a command within the docker-compose.yml?

I think you don't need to extend the existing postgres. It's okay to have another existing container running postgress which uses port 5432, because each container has its own ip address. If you want to use the existing one, run make_db.sh in the container to create the database for mattermost and configure mattermost to use it.

I presume it's OK to redirect port 80 in the app to a different port on the host, without impacting the app?

Do you want to redirect a certain port in your host to port 80 in the app? Yes, it's okay. You can do that by adding ports option in app section in docker-compose.yml.

from mattermost-docker.

Thanks again. I'll close this out for now.

from mattermost-docker.