You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2022. It is now read-only.
Perhaps your issue is realted to MM-32234 (in case the command is executed as root).
According to the v5.31 changelog the bug has been fixed in v5.31.1 (you are on v5.31.0).
I'm not specifying the user when running the exec, so maybe I guess it's root. Running the command with the user specified in the compose should avoid that issue then?
I'm not specifying the user when running the exec, so maybe I guess it's root. Running the command with the user specified in the compose should avoid that issue then?
I had the same issue (config was reset after running mattermost command, but I specifically used the root user on the command line). I was able to fix it by switching my repo to branch 'release-5.31' (commit 8b95992) and rebuilding my docker containers afterwards (upgrading Mattermost to v5.31.1).
(I'm not sure this should be here or in the
mattermost-server
issues, but since it could be docker related I start here.)When running
my Mattermost configuration was erased (Site URL, Gitlab configuration, SMTP configuration, etc.).
I'm on 2b12534, and using mostly the default
docker-compose
except forThe text was updated successfully, but these errors were encountered: