Mssql-docker: Fatal Error and Cannot Continue Running

[clarkee013]

Hello.

Just tried to run the docker image for mssql-server-linux:latest using this command:

docker run -d --name="mssql-server-linux" --net="bridge" --cap-add=SYS_PTRACE -e HOST_OS="UnRAID" -e "ACCEPT_EULA"="Y" -e "SA_PASSWORD"="ItsASecret!" -p 1433:1433/tcp -v "/mnt/user/name/SQL":"/var/opt/mssql" microsoft/mssql-server-linux:latest

The container starts but then stops straight away - in the log the below message is given:

This program has encountered a fatal error and cannot continue running.

The following diagnostic information is available:

Reason: 0x00000003
Message: result
Stacktrace: 000055d206f7ecd2 000055d206f4d5a7
Thread: 12 (application thread 0x1000)
Instance Id: 8b6a4ffc-8842-4f78-92d4-737ca2ac35a0
Crash Id: 021878ae-fd02-4e3b-9dab-b1db83a6ee6f
Build stamp: 67985f5f2388dc542a5404081e4a74fa74de2a2c312d5891062df73364f7779b

Capturing core dump and information...
No journal files were found.
No journal files were found.
Attempting to capture a dump with paldumper
/opt/mssql/bin/crash-support-functions.sh: line 185: 140 Aborted $program_dir/paldumper $dokill -p $pid -d $paldumper_dump_type_str -o $dump_filename.gdmp > $paldumper_debuglog_filename 2>&1
WARNING: Capture attempt failure detected

Attempting to capture a filtered dump with paldumper

In the crash log in /log the following info is given:

This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:

   Reason: 0x00000003
   Message: result
Stacktrace: 000055d206f7ecd2 000055d206f4d5a7 

   Process: 8 - sqlservr
    Thread: 12 (application thread 0x1000)

Instance Id: 8b6a4ffc-8842-4f78-92d4-737ca2ac35a0
Crash Id: 021878ae-fd02-4e3b-9dab-b1db83a6ee6f
Build stamp: 67985f5f2388dc542a5404081e4a74fa74de2a2c312d5891062df73364f7779b

Please can someone help me - am i missing something obvious?

Many thanks

[axelfontaine]

+1 both with CU1 and CU3

[esetnik]

+1 also with GA

[twright-msft]

@esetnik, @axelfontaine, @clarkee013 - Can you please tell us more about your environment? Are you running on Windows or Linux? If on Linux, what distribution/version and what file system?

[axelfontaine]

@twright-msft Bare Metal Ubuntu 16.04

[twright-msft]

@axelfontaine - which file system?

[axelfontaine]

@twright-msft Ext4. FWIW the issue resolved itself after I manually upgraded to kernel to 4.14 mainline.

[twright-msft]

OK thanks for letting us know @axelfontaine. Glad it's working for you now. @clarkee013 , @esetnik - can you please tell us more about your environment? Are you upgraded to kernel 4.14?

[clarkee013]

Running Linux 4.14.13-unRAID x86_64 and using docker v17.09.1-ce

thanks

[clarkee013]

and more than a month on and still the same issue... any chance of a way forward or some form of help/insight?

@twright-msft

[twright-msft]

We've had issues with unRAID in the past.

For example:
https://github.com/Microsoft/mssql-docker/issues/25

It's not a platform we test right now.
Any chance you can use Ubuntu, RHEL, or SLES?

[clarkee013]

Nope cant use Ubuntu, RHEL or SLES simply as I do not want a full VM having to spin up/down whenever I want to use one program, totally defeats the purpose of saying MS support docker in Linux environment.

Cant say I'm not surprised about the lack of help after reading thought the other silences to others that have had issues.

For anyone else using UnRaid - don't expect any help here, the folks over at MySQL have a docker that runs perfectly AND they are happy to give decent support with ideas of solutions when something needs looked at.

[whatevergeek]

hi,

I think this issue seems to be happening if you provide volume in the parameters (-v).
Perhaps, SQL Server doesn't have a stable support for it currently.

I just removed the volume param and I was able to spawn it.
docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=<password>' -p 1433:1433 -d mcr.microsoft.com/mssql/server:vNext-CTP2.0-ubuntu

Hope the SqlServer team fixes the volume issue soon.

[spikeheap]

Thanks @whatevergeek. I can confirm this issue exists on Docker for Mac (Version 2.0.0.0-beta1-mac75 (27117)), and removing the local volume mapping resolves the failure.

[KostaMadorsky]

Same here. Windows 7 x64 with docker toolbox and VirtualBox.
Works fine if you run mssql linux container without volume or if you use docker machine named volume (e.g. -v mssql:/var/opt/mssql).

When the container spins it creates the following folders only: .system, log, secrets.
data folder it missing.

On Win 10 with Docker for Windows same container works fine with a volume bound to a host directory.