Open goostleek opened 7 years ago
At the moment the only workaround for that is to use a data volume (as suggested).
any updates on this? it currently crashes on load when docker volume (-v) is used:
i talked to Anna Shrestinian the other day in the #MSTechSummit she said volumes should now work... e.g. docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=SqlServer101' -v /c/path_to_local/mssql:/var/opt/mssql -p 1433:1433 -d microsoft/mssql-server-linux:2017-GA
but seems it is still not working... any other additional setup i need to do?
Any news on the issue?
Running a container from image microsoft/mssql-server-linux
and a volume mapping ./local/folder:/var/opt/mssql/
still fails. My host is a Win10 machine.
Microsoft SQL Server 2017 (RTM-CU3-GDR) (KB4052987) - 14.0.3015.40 (X64) Dec 22 2017 16:13:22 Developer Edition (64-bit) on Linux (Ubuntu 16.04.3 LTS)
From output:
2018-02-06 00:09:05.50 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.
2018-02-06 00:09:06.03 spid7s Converting database 'master' from version 862 to the current version 869.
2018-02-06 00:09:06.04 spid7s Database 'master' running the upgrade step from version 862 to version 863.
2018-02-06 00:09:06.09 spid7s Database 'master' running the upgrade step from version 863 to version 864.
2018-02-06 00:09:06.15 spid7s Error: 17053, Severity: 16, State: 1.
2018-02-06 00:09:06.15 spid7s /var/opt/mssql/data/mastlog.ldf: Operating system error 31(A device attached to the system is not functioning.) encountered.
2018-02-06 00:09:07.21 spid7s Error: 928, Severity: 20, State: 1.
2018-02-06 00:09:07.21 spid7s During upgrade, database raised exception 9002, severity 17, state 0, address 0000000404D013DE. Use the exception number to determine the cause.
2018-02-06 00:09:07.25 spid7s Error: 9002, Severity: 17, State: 0.
2018-02-06 00:09:07.25 spid7s The transaction log for database 'master' is full due to 'NOTHING'.
I'm on Docker Cloud and deploy the container to an AWS EC2 instance and the container fails with the same error. Everything worked fine on the my mac. Container is based off microsoft/mssql-server-linux:latest image
2018-03-06 19:35:10.33 spid6s Database 'master' running the upgrade step from version 863 to version 864.
2018-03-06 19:35:10.35 spid6s Error: 17053, Severity: 16, State: 1.
2018-03-06 19:35:10.35 spid6s /var/opt/mssql/data/mastlog.ldf: Operating system error 31(A device attached to the system is not functioning.) encountered.
2018-03-06 19:35:11.36 spid6s Error: 928, Severity: 20, State: 1.
2018-03-06 19:35:11.36 spid6s During upgrade, database raised exception 9002, severity 17, state 0, address 0000000404D013DE. Use the exception number to determi
ne the cause.
2018-03-06 19:35:11.37 spid6s Error: 9002, Severity: 17, State: 0.
2018-03-06 19:35:11.37 spid6s The transaction log for database 'master' is full due to 'NOTHING'.
I have same problem with microsoft/mssql-server-linu:latest
on Windows.
PS C:\Users\spark> systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.14393 N/A Build 14393
PS C:\Users\spark> docker -v
Docker version 17.12.0-ce, build c97c6d6
PS C:\Users\spark> docker-machine -v
docker-machine.exe version 0.13.0, build 9ba6da9
But, it works for only microsoft/mssql-server-linu:2017-CU3
.
Exactly same issue, what the point to use this image at all if the volume cannot be mapped ?
@evgeny-pol You can still use volumes. Please see https://github.com/microsoft/mssql-docker/issues/52#issuecomment-288075275
Actual result
Starting the container with mounted volume by
causes the server startup failure:
Expected result
The container should start successfully, eg. when no volume is used:
Environment