Sql container will not start because of master database corruption
2020-10-15 20:49:14.08 Server In-Memory OLTP initialized on lowend machine.
2020-10-15 20:49:14.14 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
ForceFlush is enabled for this instance.
2020-10-15 20:49:14.18 spid6s Starting up database 'master'.
2020-10-15 20:49:14.19 Server Query Store settings initialized with enabled = 1,
2020-10-15 20:49:14.20 Server Software Usage Metrics is disabled.
ForceFlush feature is enabled for log durability.
2020-10-15 20:49:14.32 spid6s Error: 9003, Severity: 20, State: 9.
2020-10-15 20:49:14.32 spid6s The log scan number (2492:32:0) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2020-10-15 20:49:14.34 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.