Docker安装SQL Server遇到的问题

今天正在刷牙的时候，一个朋友叫我给他弄一个MSSQL，因为之前自己买的主机装有Docker环境，所以第一反应就是使用Docker来安装，原以为就是一句脚本的问题，结果还是花了一些时间,这里记录一下所遇到的问题

安装MSSQL

由于我的主机大概只剩六百多兆，而且docker中的mssql默认需要2G内存，所以这里我就限制了mssql的内存大小为512m，命令如下:

[root@instance-p0a4erj8 ~]# docker run --name mssql -m 512m -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=eyiadmin' -p 1433:1433 -d microsoft/mssql-server-linux
4a67d71771baabc94de453da72a215d222fcd42a2014a3e30c31690e80063eff

这时候，容器是没有启动成功,所以需要看看是什么原因:

2020-02-16 14:22:43.37 spid22s     ERROR: Unable to set system administrator password: Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols..
2020-02-16 14:22:43.37 spid22s     An error occurred during server setup. See previous errors for more information.

很明显，是密码太简单了，所以增加密码的复杂度:

docker run --name mssql -m 512m -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Eyiadmin@258' -p 1433:1433 -d microsoft/mssql-server-linux

这时候，docker logs没有错误信息

[root@instance-p0a4erj8 ~]# docker logs 120051b577ef
2020-02-16 14:24:45.35 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2020-02-16 14:24:45.44 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2020-02-16 14:24:45.44 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2020-02-16 14:24:45.45 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2020-02-16 14:24:45.49 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2020-02-16 14:24:45.59 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2020-02-16 14:24:45.70 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2020-02-16 14:24:45.83 Server      Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4 (X64) 
        Nov 30 2018 12:57:58 
        Copyright (C) 2017 Microsoft Corporation
        Developer Edition (64-bit) on Linux (Ubuntu 16.04.5 LTS)
2020-02-16 14:24:45.83 Server      UTC adjustment: 0:00
2020-02-16 14:24:45.83 Server      (c) Microsoft Corporation.
2020-02-16 14:24:45.83 Server      All rights reserved.
2020-02-16 14:24:45.83 Server      Server process ID is 4120.
2020-02-16 14:24:45.83 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2020-02-16 14:24:45.83 Server      Registry startup parameters: 
         -d /var/opt/mssql/data/master.mdf
         -l /var/opt/mssql/data/mastlog.ldf
         -e /var/opt/mssql/log/errorlog
2020-02-16 14:24:45.83 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-02-16 14:24:45.84 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-02-16 14:24:45.84 Server      Detected 410 MB of RAM. This is an informational message; no user action is required.
2020-02-16 14:24:45.84 Server      Using conventional memory in the memory manager.
2020-02-16 14:24:46.09 Server      Buffer pool extension is already disabled. No action is necessary. 
2020-02-16 14:24:46.25 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2020-02-16 14:24:46.25 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
2020-02-16 14:24:46.25 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2020-02-16 14:24:46.30 Server      The maximum number of dedicated administrator connections for this instance is '1'
2020-02-16 14:24:46.30 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-02-16 14:24:46.31 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2020-02-16 14:24:46.33 Server      In-Memory OLTP initialized on lowend machine.
2020-02-16 14:24:46.40 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-02-16 14:24:46.41 Server      Query Store settings initialized with enabled = 1, 
2020-02-16 14:24:46.42 spid6s      Starting up database 'master'.
2020-02-16 14:24:46.43 Server      Software Usage Metrics is disabled.
ForceFlush feature is enabled for log durability.
2020-02-16 14:24:46.64 spid6s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2020-02-16 14:24:46.84 spid6s      Converting database 'master' from version 862 to the current version 869.
2020-02-16 14:24:46.84 spid6s      Database 'master' running the upgrade step from version 862 to version 863.
2020-02-16 14:24:46.87 spid6s      Database 'master' running the upgrade step from version 863 to version 864.
2020-02-16 14:24:46.90 spid6s      Database 'master' running the upgrade step from version 864 to version 865.
2020-02-16 14:24:46.91 spid6s      Database 'master' running the upgrade step from version 865 to version 866.
2020-02-16 14:24:46.92 spid6s      Database 'master' running the upgrade step from version 866 to version 867.
2020-02-16 14:24:46.93 spid6s      Database 'master' running the upgrade step from version 867 to version 868.
2020-02-16 14:24:46.94 spid6s      Database 'master' running the upgrade step from version 868 to version 869.
2020-02-16 14:24:47.28 spid6s      Resource governor reconfiguration succeeded.
2020-02-16 14:24:47.29 spid6s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2020-02-16 14:24:47.29 spid6s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2020-02-16 14:24:47.36 spid6s      SQL Trace ID 1 was started by login "sa".
2020-02-16 14:24:47.38 spid6s      Server name is '120051b577ef'. This is an informational message only. No user action is required.
2020-02-16 14:24:47.42 spid6s      Starting up database 'msdb'.
2020-02-16 14:24:47.42 spid22s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2020-02-16 14:24:47.43 spid9s      Starting up database 'mssqlsystemresource'.
2020-02-16 14:24:47.43 spid18s     Password policy update was successful.
2020-02-16 14:24:47.44 spid22s     Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2020-02-16 14:24:47.45 spid9s      The resource database build version is 14.00.3048. This is an informational message only. No user action is required.
2020-02-16 14:24:47.48 spid9s      Starting up database 'model'.
2020-02-16 14:24:47.93 spid6s      The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes.  512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2020-02-16 14:24:47.95 spid9s      The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2020-02-16 14:24:47.99 spid6s      Converting database 'msdb' from version 862 to the current version 869.
2020-02-16 14:24:47.99 spid6s      Database 'msdb' running the upgrade step from version 862 to version 863.
2020-02-16 14:24:48.00 spid9s      Converting database 'model' from version 862 to the current version 869.
2020-02-16 14:24:48.00 spid9s      Database 'model' running the upgrade step from version 862 to version 863.
2020-02-16 14:24:48.02 spid18s     A self-generated certificate was successfully loaded for encryption.
2020-02-16 14:24:48.03 spid9s      Database 'model' running the upgrade step from version 863 to version 864.
2020-02-16 14:24:48.03 spid18s     Server is listening on [ 'any' <ipv4> 1433].
2020-02-16 14:24:48.04 spid6s      Database 'msdb' running the upgrade step from version 863 to version 864.
2020-02-16 14:24:48.06 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2020-02-16 14:24:48.06 Server      Dedicated admin connection support was established for listening locally on port 1434.
2020-02-16 14:24:48.09 spid18s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2020-02-16 14:24:48.09 spid9s      Database 'model' running the upgrade step from version 864 to version 865.
2020-02-16 14:24:48.11 spid6s      Database 'msdb' running the upgrade step from version 864 to version 865.
2020-02-16 14:24:48.13 spid9s      Database 'model' running the upgrade step from version 865 to version 866.
2020-02-16 14:24:48.14 spid6s      Database 'msdb' running the upgrade step from version 865 to version 866.
2020-02-16 14:24:48.19 spid6s      Database 'msdb' running the upgrade step from version 866 to version 867.
2020-02-16 14:24:48.19 spid9s      Database 'model' running the upgrade step from version 866 to version 867.
2020-02-16 14:24:48.24 spid6s      Database 'msdb' running the upgrade step from version 867 to version 868.
2020-02-16 14:24:48.24 spid9s      Database 'model' running the upgrade step from version 867 to version 868.
2020-02-16 14:24:48.28 spid6s      Database 'msdb' running the upgrade step from version 868 to version 869.
2020-02-16 14:24:48.34 spid9s      Database 'model' running the upgrade step from version 868 to version 869.
2020-02-16 14:24:48.49 spid9s      Polybase feature disabled.
2020-02-16 14:24:48.49 spid9s      Clearing tempdb database.
2020-02-16 14:24:49.21 spid9s      Starting up database 'tempdb'.
2020-02-16 14:24:49.56 spid9s      The tempdb database has 1 data file(s).
2020-02-16 14:24:49.57 spid24s     The Service Broker endpoint is in disabled or stopped state.
2020-02-16 14:24:49.57 spid24s     The Database Mirroring endpoint is in disabled or stopped state.
2020-02-16 14:24:49.59 spid24s     Service Broker manager has started.
2020-02-16 14:24:49.70 spid6s      Recovery is complete. This is an informational message only. No user action is required.
2020-02-16 14:24:49.74 spid22s     The default language (LCID 0) has been set for engine and full-text services.
2020-02-16 14:27:02.05 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:02.05 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:08.84 Logon       Error: 17806, Severity: 20, State: 14.
2020-02-16 14:27:08.84 Logon       SSPI handshake failed with error code 0x80090305, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The operating system error code indicates the cause of failure. The requested security package does not exist   [CLIENT: 212.92.97.23]
2020-02-16 14:27:08.84 Logon       Error: 18452, Severity: 14, State: 1.
2020-02-16 14:27:08.84 Logon       Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. [CLIENT: 212.92.97.23]
2020-02-16 14:27:10.80 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:10.80 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:13.64 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:13.64 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:14.98 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:14.98 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:19.34 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:19.34 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:24.32 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:24.32 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:25.66 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:25.66 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:27.01 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:27.01 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:28.37 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:28.37 Logon       Login failed for user 'vice'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:29.73 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:29.73 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:40.86 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:27:40.86 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:42.22 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:42.22 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:44.19 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:44.19 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:45.54 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:45.54 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:46.88 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:46.88 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:48.99 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:48.99 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:27:53.35 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:27:53.35 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:02.40 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:02.40 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:06.74 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:06.74 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:08.08 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:08.08 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:10.07 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:10.07 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:11.41 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:11.41 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:12.77 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:12.77 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:21.46 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:21.46 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:22.80 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:22.80 Logon       Login failed for user 'mssqla'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:24.80 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:24.80 Logon       Login failed for user 'kisadmin'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:26.94 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:26.94 Logon       Login failed for user 'hbv7'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:28.31 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:28.31 Logon       Login failed for user 'bwsa'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:31.56 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:31.56 Logon       Login failed for user 'ps'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:32.89 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:28:32.89 Logon       Login failed for user 'uep'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:41.08 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:41.08 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:28:42.45 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:28:42.45 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:07.91 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:07.91 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:09.88 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:09.88 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:11.25 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:11.25 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:12.60 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:12.60 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:17.08 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:17.08 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:22.18 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:22.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:27.22 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:27.22 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:29.17 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:29.17 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:33.00 Logon       Error: 18456, Severity: 14, State: 5.
2020-02-16 14:29:33.00 Logon       Login failed for user '401hk'. Reason: Could not find a login matching the name provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:34.36 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:34.36 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:35.72 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:35.72 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:37.08 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:37.08 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:39.97 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:39.97 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]
2020-02-16 14:29:42.61 Logon       Error: 18456, Severity: 14, State: 8.
2020-02-16 14:29:42.61 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: 212.92.97.23]

而且，我的CPU飙升值100%,内存也只剩200M左右，但是没过一会，docker容器依然退了，我最开始没有想明白，最后，我才知道原来是因为内存不够用的原因，所以把一些其他的docker资源清理掉后再把mssql的内存加大

docker run --name mssql -m 2048m -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Eyiadmin@258' -p 1433:1433 -d microsoft/mssql-server-linux

重新启动，mssql的容器就正常运行了。

[root@instance-p0a4erj8 ~]# docker logs 5f913c39e1af
2020-02-16 14:45:58.06 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2020-02-16 14:45:58.18 Server      Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2020-02-16 14:45:58.19 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2020-02-16 14:45:58.24 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2020-02-16 14:45:58.26 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2020-02-16 14:45:58.36 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2020-02-16 14:45:58.41 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2020-02-16 14:45:58.57 Server      Microsoft SQL Server 2017 (RTM-CU13) (KB4466404) - 14.0.3048.4 (X64) 
        Nov 30 2018 12:57:58 
        Copyright (C) 2017 Microsoft Corporation
        Developer Edition (64-bit) on Linux (Ubuntu 16.04.5 LTS)
2020-02-16 14:45:58.57 Server      UTC adjustment: 0:00
2020-02-16 14:45:58.57 Server      (c) Microsoft Corporation.
2020-02-16 14:45:58.57 Server      All rights reserved.
2020-02-16 14:45:58.57 Server      Server process ID is 4120.
2020-02-16 14:45:58.58 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2020-02-16 14:45:58.58 Server      Registry startup parameters: 
         -d /var/opt/mssql/data/master.mdf
         -l /var/opt/mssql/data/mastlog.ldf
         -e /var/opt/mssql/log/errorlog
2020-02-16 14:45:58.58 Server      SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-02-16 14:45:58.58 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-02-16 14:45:58.59 Server      Detected 1639 MB of RAM. This is an informational message; no user action is required.
2020-02-16 14:45:58.59 Server      Using conventional memory in the memory manager.
2020-02-16 14:45:58.83 Server      Buffer pool extension is already disabled. No action is necessary. 
2020-02-16 14:45:59.10 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2020-02-16 14:45:59.10 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
2020-02-16 14:45:59.11 Server      Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2020-02-16 14:45:59.16 Server      The maximum number of dedicated administrator connections for this instance is '1'
2020-02-16 14:45:59.16 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-02-16 14:45:59.17 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2020-02-16 14:45:59.18 Server      In-Memory OLTP initialized on lowend machine.
2020-02-16 14:45:59.35 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-02-16 14:45:59.36 Server      Query Store settings initialized with enabled = 1, 
2020-02-16 14:45:59.39 Server      Software Usage Metrics is disabled.
2020-02-16 14:45:59.39 spid7s      Starting up database 'master'.
ForceFlush feature is enabled for log durability.
2020-02-16 14:45:59.96 spid7s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2020-02-16 14:46:00.32 spid7s      Converting database 'master' from version 862 to the current version 869.
2020-02-16 14:46:00.32 spid7s      Database 'master' running the upgrade step from version 862 to version 863.
2020-02-16 14:46:00.39 spid7s      Database 'master' running the upgrade step from version 863 to version 864.
2020-02-16 14:46:00.44 spid7s      Database 'master' running the upgrade step from version 864 to version 865.
2020-02-16 14:46:00.46 spid7s      Database 'master' running the upgrade step from version 865 to version 866.
2020-02-16 14:46:00.47 spid7s      Database 'master' running the upgrade step from version 866 to version 867.
2020-02-16 14:46:00.49 spid7s      Database 'master' running the upgrade step from version 867 to version 868.
2020-02-16 14:46:00.51 spid7s      Database 'master' running the upgrade step from version 868 to version 869.
2020-02-16 14:46:00.81 spid7s      Resource governor reconfiguration succeeded.
2020-02-16 14:46:00.81 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2020-02-16 14:46:00.81 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2020-02-16 14:46:00.89 spid7s      SQL Trace ID 1 was started by login "sa".
2020-02-16 14:46:00.92 spid7s      Server name is '5f913c39e1af'. This is an informational message only. No user action is required.
2020-02-16 14:46:00.94 spid22s     Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2020-02-16 14:46:00.94 spid22s     Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2020-02-16 14:46:00.95 spid7s      Starting up database 'msdb'.
2020-02-16 14:46:00.95 spid9s      Starting up database 'mssqlsystemresource'.
2020-02-16 14:46:00.97 spid19s     Password policy update was successful.
2020-02-16 14:46:00.98 spid9s      The resource database build version is 14.00.3048. This is an informational message only. No user action is required.
2020-02-16 14:46:01.03 spid9s      Starting up database 'model'.
2020-02-16 14:46:01.42 spid7s      The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes.  512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2020-02-16 14:46:01.42 spid9s      The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes.  2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2020-02-16 14:46:01.51 spid9s      Converting database 'model' from version 862 to the current version 869.
2020-02-16 14:46:01.51 spid9s      Database 'model' running the upgrade step from version 862 to version 863.
2020-02-16 14:46:01.53 spid7s      Converting database 'msdb' from version 862 to the current version 869.
2020-02-16 14:46:01.54 spid7s      Database 'msdb' running the upgrade step from version 862 to version 863.
2020-02-16 14:46:01.59 spid19s     A self-generated certificate was successfully loaded for encryption.
2020-02-16 14:46:01.64 spid19s     Server is listening on [ 'any' <ipv4> 1433].
2020-02-16 14:46:01.64 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2020-02-16 14:46:01.64 Server      Dedicated admin connection support was established for listening locally on port 1434.
2020-02-16 14:46:01.65 spid9s      Database 'model' running the upgrade step from version 863 to version 864.
2020-02-16 14:46:01.66 spid19s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2020-02-16 14:46:01.69 spid9s      Database 'model' running the upgrade step from version 864 to version 865.
2020-02-16 14:46:01.78 spid9s      Database 'model' running the upgrade step from version 865 to version 866.
2020-02-16 14:46:01.78 spid7s      Database 'msdb' running the upgrade step from version 863 to version 864.
2020-02-16 14:46:01.79 spid9s      Database 'model' running the upgrade step from version 866 to version 867.
2020-02-16 14:46:01.80 spid7s      Database 'msdb' running the upgrade step from version 864 to version 865.
2020-02-16 14:46:01.81 spid9s      Database 'model' running the upgrade step from version 867 to version 868.
2020-02-16 14:46:01.82 spid7s      Database 'msdb' running the upgrade step from version 865 to version 866.
2020-02-16 14:46:01.83 spid7s      Database 'msdb' running the upgrade step from version 866 to version 867.
2020-02-16 14:46:01.84 spid9s      Database 'model' running the upgrade step from version 868 to version 869.
2020-02-16 14:46:01.84 spid7s      Database 'msdb' running the upgrade step from version 867 to version 868.
2020-02-16 14:46:01.86 spid7s      Database 'msdb' running the upgrade step from version 868 to version 869.
2020-02-16 14:46:01.97 spid9s      Polybase feature disabled.
2020-02-16 14:46:01.97 spid9s      Clearing tempdb database.
2020-02-16 14:46:02.57 spid9s      Starting up database 'tempdb'.
2020-02-16 14:46:02.93 spid9s      The tempdb database has 1 data file(s).
2020-02-16 14:46:02.94 spid22s     The Service Broker endpoint is in disabled or stopped state.
2020-02-16 14:46:02.94 spid22s     The Database Mirroring endpoint is in disabled or stopped state.
2020-02-16 14:46:02.96 spid22s     Service Broker manager has started.
2020-02-16 14:46:03.09 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2020-02-16 14:46:03.17 spid24s     The default language (LCID 0) has been set for engine and full-text services.

最后我们把容器中MSSQL的数据目录挂载到宿主机目录,并且在服务器重启后自动启动容器:

docker run --name mssql -m 2048m -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Eyiadmin@258' -v /root/mssql:/var/opt/mssql -p 1433:1433 --restart=always -d microsoft/mssql-server-linux 

或者通过命令修改:

docker container update --restart=always 容器名字

还原数据库

复制备份数据至容器内

我们需要先把备份的.bak文件复制到Docker中，

docker cp /root/JewelryIdentification_db.bak mssql:/var/opt/mssql/backup/

这里需要注意，需要先创建目录，不然会提示文件夹不存在:

[root@instance-p0a4erj8 ~]# docker cp /root/JewelryIdentification_db_Dev.bak mssql:/var/opt/mssql/backup/
no such directory

所以先创建文件夹:

docker exec -it mssql mkdir -p /var/opt/mssql/backup/

然后在执行文件复制命令

docker cp /root/JewelryIdentification_db_Dev.bak mssql:/var/opt/mssql/backup/

还原备份文件

在将数据备份文件复制到容器中后，可以借助mssql的提供的命令工具进行数据还原，首先使用RESTORE FILELISTONLY命令列出备份数据文件的逻辑名

[root@instance-p0a4erj8 ~]# docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P 'Eyiadmin@258' -Q 'RESTORE FILELISTONLY FROM DISK = "/var/opt/mssql/backup/JewelryIdentification_db_Dev.bak"' | tr -s ' ' | cut -d ' ' -f 1-2
LogicalName PhysicalName
-------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
JewelryIdentification_db_Dev D:\Web\JewelryIdentification\Database\JewelryIdentification_db_Dev.mdf
JewelryIdentification_db_Dev_log D:\Web\JewelryIdentification\Database\JewelryIdentification_db_Dev_log.ldf

(2 rows

执行命令还原数据库:

docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P 'Eyiadmin@258' -Q 'RESTORE DATABASE JewelryIdentification_db_Dev FROM DISK = "/var/opt/mssql/backup/JewelryIdentification_db_Dev.bak" WITH MOVE "JewelryIdentification_db_Dev" TO "/var/opt/mssql/data/JewelryIdentification_db_Dev.mdf", MOVE "JewelryIdentification_db_Dev_log" TO "/var/opt/mssql/data/JewelryIdentification_db_Dev_log.ldf"'

最终成功:

[root@instance-p0a4erj8 ~]# docker exec -it mssql /opt/mssql-tools/bin/sqlcmd -S localhost -U SA -P 'Eyiadmin@258' -Q 'RESTORE DATABASE JewelryIdentification_db_Dev FROM DISK = "/var/opt/mssql/backup/JewelryIdentification_db_Dev.bak" WITH MOVE "JewelryIdentification_db_Dev" TO "/var/opt/mssql/data/JewelryIdentification_db_Dev.mdf", MOVE "JewelryIdentification_db_Dev_log" TO "/var/opt/mssql/data/JewelryIdentification_db_Dev_log.ldf"'
Processed 960 pages for database 'JewelryIdentification_db_Dev', file 'JewelryIdentification_db_Dev' on file 1.
Processed 2 pages for database 'JewelryIdentification_db_Dev', file 'JewelryIdentification_db_Dev_log' on file 1.
Converting database 'JewelryIdentification_db_Dev' from version 706 to the current version 869.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 706 to version 770.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 770 to version 771.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 771 to version 772.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 772 to version 773.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 773 to version 774.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 774 to version 775.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 775 to version 776.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 776 to version 777.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 777 to version 778.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 778 to version 779.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 779 to version 780.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 780 to version 781.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 781 to version 782.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 782 to version 801.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 801 to version 802.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 802 to version 803.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 803 to version 804.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 804 to version 805.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 805 to version 806.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 806 to version 807.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 807 to version 808.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 808 to version 809.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 809 to version 810.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 810 to version 811.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 811 to version 812.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 812 to version 813.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 813 to version 814.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 814 to version 815.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 815 to version 816.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 816 to version 817.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 817 to version 818.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 818 to version 819.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 819 to version 820.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 820 to version 821.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 821 to version 822.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 822 to version 823.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 823 to version 824.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 824 to version 825.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 825 to version 826.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 826 to version 827.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 827 to version 828.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 828 to version 829.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 829 to version 830.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 830 to version 831.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 831 to version 832.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 832 to version 833.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 833 to version 834.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 834 to version 835.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 835 to version 836.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 836 to version 837.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 837 to version 838.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 838 to version 839.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 839 to version 840.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 840 to version 841.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 841 to version 842.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 842 to version 843.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 843 to version 844.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 844 to version 845.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 845 to version 846.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 846 to version 847.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 847 to version 848.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 848 to version 849.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 849 to version 850.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 850 to version 851.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 851 to version 852.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 852 to version 853.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 853 to version 854.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 854 to version 855.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 855 to version 856.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 856 to version 857.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 857 to version 858.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 858 to version 859.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 859 to version 860.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 860 to version 861.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 861 to version 862.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 862 to version 863.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 863 to version 864.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 864 to version 865.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 865 to version 866.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 866 to version 867.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 867 to version 868.
Database 'JewelryIdentification_db_Dev' running the upgrade step from version 868 to version 869.
RESTORE DATABASE successfully processed 962 pages in 0.129 seconds (58.260 MB/sec).

至此Docker搭建MSSQL顺利完成

今天朋友叫我给他备份一个数据库下来，那么我就只有先执行备份命令，由于我将mssql的数据目录挂载到宿主机目录，即可直接复制下来即可,那就来吧

BACKUP DATABASE [JewelryIdentification_db_Dev]
TO
  DISK = N'/var/opt/mssql/backup/JewelryIdentification_db_Dev.bak'
WITH
  NAME = N'JewelryIdentification_db_Dev - Backup',
  NOFORMAT, NOINIT, SKIP,
  STATS = 5

我的挂载目录是/root/mssql:/var/opt/mssql,这时候来看看文件

[root@instance-p0a4erj8 ~]# cd /root/mssql/backup
[root@instance-p0a4erj8 backup]# tree
.
├── JewelryIdentification_db_Dev_20200307.bak
└── JewelryIdentification_db_Dev.bak