Running docker-compose exec app mattermost erase configuration

mattermost / mattermost-docker

Deprecated

Apache License 2.0

964 stars 575 forks source link

Running docker-compose exec app mattermost erase configuration #516

Open Holt59 opened 3 years ago

Holt59 commented 3 years ago

(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

docker-compose exec app mattermost channel modify ...

my Mattermost configuration was erased (Site URL, Gitlab configuration, SMTP configuration, etc.).

I'm on 2b12534f900f51a485c47bcd880a61df1b20beb7, and using mostly the default docker-compose except for

the team edition
the volumes for the various containers

duncan1707 commented 3 years ago

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).

Holt59 commented 3 years ago

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?

duncan1707 commented 3 years ago

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 https://github.com/mattermost/mattermost-docker/commit/8b95992a92edcf7c222641626d547b184cd5477d) and rebuilding my docker containers afterwards (upgrading Mattermost to v5.31.1).

bor8 commented 3 years ago

Same. Does it only affect config.json? Luckily I have good backup.