failed to start container

[jelmd]

migration-assist mysql <DSN> --mattermost-version=8.1.2 --save-diff --full-schema-check fails with:

2025-02-05 16:51:12 pinging mysql...
2025-02-05 16:51:12 connected to mysql successfully...
Output file already exists, do you want to overwrite it? [y/N]: y
2025-02-05 16:51:14 setting up a test MySQL instance...
2025/02/05 16:51:14 failed to start container: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?: failed to create container

Why does it need docker bloat for schema checking?

[isacikgoz]

Hey @jelmd it is creating a temporary database and runs the migrations from scratch. So that we can have a schema that we can compare according to your current database. Probably it's better to document it why we need docker here. The gist is we create a separate instance of MySQL to be able to "replicate" the expected schema.

[jelmd]

@isacikgoz Ahh, ok. Expected that this checks in addition some other system settings/catalogs, which usually do not really have a negative impact on the mattermost db [migration]. IMHO at least a hint, that this requires docker for duplication would help.