mattermost-docker icon indicating copy to clipboard operation
mattermost-docker copied to clipboard

Running docker-compose exec app mattermost erase configuration

Open Holt59 opened this issue 3 years ago • 4 comments

(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

Holt59 avatar Feb 17 '21 08:02 Holt59

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

duncan1707 avatar Feb 23 '21 15:02 duncan1707

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?

Holt59 avatar Feb 23 '21 16:02 Holt59

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

duncan1707 avatar Feb 23 '21 18:02 duncan1707

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

bor8 avatar May 04 '21 14:05 bor8