Skip to content
This repository has been archived by the owner on May 20, 2022. It is now read-only.

Sync Releases to mattermost-server #535

Open
laktak opened this issue May 17, 2021 · 11 comments
Open

Sync Releases to mattermost-server #535

laktak opened this issue May 17, 2021 · 11 comments

Comments

@laktak
Copy link

laktak commented May 17, 2021

Would it be possible to do releases in step with mattermost-server?

Currently there is a gap between mattermost-server (v5.35.0) and mattermost-docker (v5.33.3).

@maxraab
Copy link

maxraab commented May 18, 2021

They normally keep the versions in sync. I guess it's paused due to this warning.

@laktak
Copy link
Author

laktak commented May 18, 2021

Thank you for the information.

I didn't think that would be a problem since the images are tagged with their versions. Even if you run into this you can revert to an older version of the image.

@rubentrf
Copy link

As a temporary solution to this: if you bump the MM_VERSION here and run docker-compose build and up again, the new image with the new release should be built and deployed, right?

But I agree, it would be great if they manage keep it in sync, let's give them a little more time.

@laktak
Copy link
Author

laktak commented May 19, 2021

As a temporary solution to this: if you bump the MM_VERSION here and run docker-compose build and up again, the new image with the new release should be built and deployed, right?

Good idea. Care to try and let us know if it works? ;-)

@rubentrf
Copy link

Probably not today, but I’d like to try it, I’ll let you know if it works

@maxraab
Copy link

maxraab commented May 19, 2021

Good idea. Care to try and let us know if it works? ;-)

Well, I do it this way and it does work. Keep in mind that you need to use Postgres >= v10 to use recent versions. So you eihter need to upgrade the database before or start with a fresh installation and the desired version.

@nathcoad
Copy link

I tried updating the version in docker-compose to 5.35.0 and rebuilding. The app container starts fine, but the update to the web container to work as an unprivileged user doesn't start successfully for me. I get the following error messages, only way I could see to get the container to start again was to revert to the previous nginx base image (nginx:mainline-alpine).

linking plain config
2021/05/20 13:00:09 [emerg] 1#1: bind() to 0.0.0.0:80 failed (13: Permission denied)
nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)
ln: /etc/nginx/conf.d/mattermost.conf: File exists
sed: can't create temp file '/etc/nginx/conf.d/mattermost.confXXXXXX': Permission denied
sed: can't create temp file '/etc/nginx/conf.d/mattermost.confXXXXXX': Permission denied

I'm not sure why this happens, because the Dockerfile contains the command "chown -R nginx:nginx /etc/nginx/conf.d && " which should allow sed to create temp files. Any ideas where else I can look?

@rubentrf
Copy link

rubentrf commented May 21, 2021

I just tested changing the MM_VERSION to 5.35.1 and docker-compose build --no-cache then docker-compose down and docker-compose up -d and everything seems to be working fine 🎉 .

I had previously upgraded Postgres to version 12 via a dump and restore of the data.

@nathcoad
Copy link

I previously upgraded Postgres to version 13.2 via the script at #489 (comment)

I'll try deleting the volumes for the web container and then running another docker-compose build, in case something weird is happening with the old volumes.

@nathcoad
Copy link

Yep that fixed my issue with the unprivileged nginx build.

@avoulk
Copy link

avoulk commented May 27, 2021

I just tested changing the MM_VERSION to 5.35.1 and docker-compose build --no-cache then docker-compose down and docker-compose up -d and everything seems to be working fine 🎉 .

I had previously upgraded Postgres to version 12 via a dump and restore of the data.

I confirm that this works. Just upgraded from 5.33.1 to 5.35.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants