-
Notifications
You must be signed in to change notification settings - Fork 575
Sync Releases to mattermost-server #535
Comments
They normally keep the versions in sync. I guess it's paused due to this warning. |
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. |
As a temporary solution to this: if you bump the But I agree, it would be great if they manage keep it in sync, let's give them a little more time. |
Good idea. Care to try and let us know if it works? ;-) |
Probably not today, but I’d like to try it, I’ll let you 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. |
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 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? |
I just tested changing the I had previously upgraded Postgres to version 12 via a dump and restore of the data. |
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. |
Yep that fixed my issue with the unprivileged nginx build. |
I confirm that this works. Just upgraded from |
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).
The text was updated successfully, but these errors were encountered: