Upload image to Docker Hub about mattermost-docker

[eungjun-yi]

@it33 Would you update the image?

[StianOvrevage]

+1 - Would love to see 3.0 on docker hub. Having a bit of challenges setting up mattermail plugin which is optimized for 3.0.

[it33]

We should, @StianOvrevage would you join us on https://pre-release.mattermost.com/core in the Developers channel? Please just post there and we can figure out how to get this done. Thanks so much for creating mattermail, would love to have you in discussions with the core team,

[xcompass]

@it33, I have a fork that published to dockerhub. Basically you will need to create one dockerhub repo for each component in this repo and point each dockerhub repo to different dockerfiles. so you will have mattermost/app, mattermost/db, etc, on dockerhub.

+1 for this so that I can get rid of my fork.

[StianOvrevage]

Credit for mattermail should go to @rodrigocorsi2 and not me! But I'll join you in the dev channel anyhow :)

[andymac4182]

It would be great to see this get submitted as a official image to dockerhub. Not sure what is involved but would make it simple to get started and up to date.

[it33]

Sorry for late reply, @crspeller was working on this and he's away for the holiday weekend in Canada, @xcompass, is there a PR you can do to help prepare this repo to get pushed to Docker Hub? I'm not familiar with setup. @npcode, wondering if you have any thoughts?

[eungjun-yi]

@it33 I completely agree with uploading the images in this repository to dockerhub. It would be nice if I can help it.

[xcompass]

@it33 you have all the code you need. No need to change the code or any PR. You just need to do the setup in docker hub. Creates three automated builds, one for app, one for db and one for web. In each build, change dockerfile location to the correct path,e.g. for app, it should be /app

Then you will have three automated build images. That's it.

[eungjun-yi]

@xcompass @it33 Additionally we can send a PR to https://github.com/docker-library/official-images to make them official images which can be found in https://hub.docker.com/explore/.

[xcompass]

Good idea!

[it33]

Thanks @npcode, @xcompass when @crspeller is back he can review and approve the ideas. Sorry for the delay, our monitoring systems in Mattermost work on /platform but we don't have them setup for /mattermost-docker yet. @esethna is back this week and we can ask his help to connect up all the Mattermost projects outside of /platform.

Please do feel free to join our Developers channel on our Mattermost instance if you'd like to be more involved in the community.

[wgorski-antrego]

As I can see, you already have a docker repository for mattermost: https://hub.docker.com/r/mattermost/platform/~/dockerfile/.
Looking at the Dockerfile, it seems like the change would be really trivial. Assuming that the location of the mattermost.tar.gz file on s3 has not changed, perhaps you would just have to rebuild the docker image and push it as version 3.0?

[crspeller]

I have redone the old preview image. It now lives here: https://hub.docker.com/r/mattermost/mattermost-preview/
With a new single line install:

docker run --name mattermost-preview -d --publish 8065:8065 mattermost/mattermost-preview

For this production image I have created three automated builds:
https://hub.docker.com/r/mattermost/mattermost-prod-app/
https://hub.docker.com/r/mattermost/mattermost-prod-db/
https://hub.docker.com/r/mattermost/mattermost-prod-web/

However the web autobuild fails with

Build failed: lstat cert/cert.pem: no such file or directory

@npcode Can we have your help fixing the web image then performing any necessary updates to pull the images from these locations.
Thanks!

[eungjun-yi]

@crspeller To fix the problem, we should not try to copy cert files into web container. I'll modify web/Dockerfile and docker-compose.yml to mount the files instead.

[eungjun-yi]

@crspeller I have just removed the dependency on cert files. Would you please try it again?

[crspeller]

@npcode Seems to have worked! After your done modifying the compose files to use the new images on docker hub. Can you tag the repository 3.0. That way a tag will be created in dockerhub so people can pull a 3.0 image.

[eungjun-yi]

@crspeller

Can you tag the repository 3.0

Well, why not 3.0.2?

[eungjun-yi]

@crspeller I have tagged this repository as 3, 3.0 and 3.0.2. I hope what I did doesn't conflict with the tagging convention of dockerhub.

[crspeller]

@npcode In the past we have not tagged dot releases. But it's fine if you want to maintain that.
I think everything is done for this issue. Closing.