for-mac
for-mac copied to clipboard
docker
Mac M3 Sonoma 14.6.1 - MSSQL Error Exited (139)
Description
I’ve tried using versions 4.32.0, 4.27.2, 4.26.1, 4.26.0, and 4.20.1. In all cases, the startup was successful, and I was able to connect. However, after about 5 minutes, the process exits with Error Code 139. Even after a normal reboot, the issue persists, and it still results in Exited (139).
Reproduce
docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=Password123456' --name sql_server --platform linux/amd64 -p 1433:1433 -d mcr.microsoft.com/mssql/server:2022-latest
Expected behavior
Not crashing
docker version
Client:
Version: 27.0.3
API version: 1.46
Go version: go1.21.11
Git commit: 7d4bcd8
Built: Fri Jun 28 23:59:41 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.32.0 (157355)
Engine:
Version: 27.0.3
API version: 1.46 (minimum version 1.24)
Go version: go1.21.11
Git commit: 662f78c
Built: Sat Jun 29 00:02:44 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.18
GitCommit: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
runc:
Version: 1.7.18
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client:
Version: 27.0.3
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.15.1-desktop.1
Path: /Users/kevincheng/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.28.1-desktop.1
Path: /Users/kevincheng/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.32
Path: /Users/kevincheng/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.14
Path: /Users/kevincheng/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/kevincheng/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.25
Path: /Users/kevincheng/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/kevincheng/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: /Users/kevincheng/.docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /Users/kevincheng/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.10.0
Path: /Users/kevincheng/.docker/cli-plugins/docker-scout
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 1
Server Version: 27.0.3
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.6.32-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 8
Total Memory: 7.657GiB
Name: docker-desktop
ID: 1ecc11c7-aa2b-46be-b824-6679c2579d99
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/kevincheng/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
FCD7F5C4-CE9A-4B52-8B29-4880F70C1F67/20240810111527
Additional Info
CPU limit to 1 seems like work fine
I've started getting the same issue on 4.33.0. I can confirm that setting the CPU limit to 1 fixes/mitigates the problem.
Full output below:
docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=testtest123" \
-p 1433:1433 \
mcr.microsoft.com/mssql/server:2017-latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
SQL Server 2017 will run as non-root by default.
This container is running as user root.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
2024-08-27 11:02:21.27 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2024-08-27 11:02:21.30 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.
2024-08-27 11:02:21.31 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2024-08-27 11:02:21.31 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2024-08-27 11:02:21.31 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2024-08-27 11:02:21.32 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2024-08-27 11:02:21.33 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2024-08-27 11:02:21.36 Server Microsoft SQL Server 2017 (RTM-CU31-GDR) (KB5029376) - 14.0.3465.1 (X64)
Jul 30 2023 15:31:58
Copyright (C) 2017 Microsoft Corporation
Developer Edition (64-bit) on Linux (Ubuntu 18.04.6 LTS)
2024-08-27 11:02:21.36 Server UTC adjustment: 0:00
2024-08-27 11:02:21.36 Server (c) Microsoft Corporation.
2024-08-27 11:02:21.36 Server All rights reserved.
2024-08-27 11:02:21.36 Server Server process ID is 396.
2024-08-27 11:02:21.36 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2024-08-27 11:02:21.37 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2024-08-27 11:02:21.37 Server SQL Server detected 1 sockets with 12 cores per socket and 12 logical processors per socket, 12 total logical processors; using 12 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-08-27 11:02:21.37 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-08-27 11:02:21.37 Server Detected 6271 MB of RAM. This is an informational message; no user action is required.
2024-08-27 11:02:21.37 Server Using conventional memory in the memory manager.
2024-08-27 11:02:21.38 Server Page exclusion bitmap is enabled.
2024-08-27 11:02:21.45 Server Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores.
2024-08-27 11:02:21.49 Server Buffer pool extension is already disabled. No action is necessary.
2024-08-27 11:02:21.58 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2024-08-27 11:02:21.59 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2024-08-27 11:02:21.59 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'].
2024-08-27 11:02:21.63 Server Query Store settings initialized with enabled = 1,
SetThreadAffinity failed: 87
2024-08-27 11:02:21.64 Server The maximum number of dedicated administrator connections for this instance is '1'
2024-08-27 11:02:21.65 Server Node configuration: node 0: CPU mask: 0x000000000000003f:0 Active CPU mask: 0x000000000000003f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2024-08-27 11:02:21.65 Server Node configuration: node 1: CPU mask: 0x0000000000000fc0:0 Active CPU mask: 0x0000000000000fc0:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2024-08-27 11:02:21.66 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.
2024-08-27 11:02:21.67 Server In-Memory OLTP initialized on lowend machine.
2024-08-27 11:02:21.71 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.
2024-08-27 11:02:21.73 Server Software Usage Metrics is disabled.
2024-08-27 11:02:21.74 spid7s Starting up database 'master'.
ForceFlush feature is enabled for log durability.
2024-08-27 11:02:21.78 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.
2024-08-27 11:02:21.89 spid7s Converting database 'master' from version 862 to the current version 869.
2024-08-27 11:02:21.89 spid7s Database 'master' running the upgrade step from version 862 to version 863.
2024-08-27 11:02:21.93 spid7s Database 'master' running the upgrade step from version 863 to version 864.
2024-08-27 11:02:21.95 spid7s Database 'master' running the upgrade step from version 864 to version 865.
2024-08-27 11:02:21.95 spid7s Database 'master' running the upgrade step from version 865 to version 866.
2024-08-27 11:02:21.95 spid7s Database 'master' running the upgrade step from version 866 to version 867.
2024-08-27 11:02:21.95 spid7s Database 'master' running the upgrade step from version 867 to version 868.
2024-08-27 11:02:21.96 spid7s Database 'master' running the upgrade step from version 868 to version 869.
This program has encountered a fatal error and cannot continue running at Tue Aug 27 11:02:22 2024
The following diagnostic information is available:
Reason: 0x00000001
Signal: SIGABRT - Aborted (6)
Stack:
IP Function
---------------- --------------------------------------
000055555569e9ec <unknown>
000055555569e432 <unknown>
000055555569da41 <unknown>
00007ffffcd2af10 killpg+0x40
00007ffffcd2ae87 gsignal+0xc7
00007ffffcd2c7f1 abort+0x141
0000555555632672 <unknown>
00005555556b5204 <unknown>
00005555556e81f8 <unknown>
00005555556e7fda <unknown>
000055555563e4ea <unknown>
000055555563e13f <unknown>
Process: 9 - sqlservr
Thread: 154 (application thread 0x260)
Instance Id: 78d4d1eb-8c3c-4fd6-92df-a3a2574bcb5a
Crash Id: b1fb2d29-4392-4e3b-96b4-1c2b759ba25d
Build stamp: 388f6c66c6dbc4da12ba35a003fcb9b5e0f65b6bc460dbf45ba9cf2562768e67
Distribution: Ubuntu 18.04.6 LTS
Processors: 12
Total Memory: 8219254784 bytes
Timestamp: Tue Aug 27 11:02:22 2024
Last errno: 2
Last errno text: No such file or directory
Capturing a dump of 9
FAILED to capture a dump. Details in paldumper log.
Executing: /opt/mssql/bin/handle-crash.sh with parameters
handle-crash.sh
/opt/mssql/bin/sqlservr
9
/opt/mssql/bin
/var/opt/mssql/log/
78d4d1eb-8c3c-4fd6-92df-a3a2574bcb5a
b1fb2d29-4392-4e3b-96b4-1c2b759ba25d
Ubuntu 18.04.6 LTS
Capturing core dump and information to /var/opt/mssql/log...
dmesg: read kernel buffer failed: Operation not permitted
/usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
/usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
Tue Aug 27 11:02:27 UTC 2024 Capturing program information
Tue Aug 27 11:02:28 UTC 2024 Attempting to capture a dump with paldumper for pid 9
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper for pid 9
WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details
Tue Aug 27 11:02:28 UTC 2024 Attempting to capture a dump with gdb
Tue Aug 27 11:02:28 UTC 2024 Captured a dump with gdb
Tue Aug 27 11:02:28 UTC 2024 Capturing program binaries
Tue Aug 27 11:02:30 UTC 2024 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.08_27_2024_11_02_22.9.d
is there any update on this issue? I had to downgrade to 4.32 to make it work. Trying running MSSql Server sqledge on Mac ARM chip.
This program has encountered a fatal error and cannot continue running at Sat Mar 29 10:54:41 2025 The following diagnostic information is available:
Reason: 0x00000001
Signal: SIGABRT - Aborted (6)
Stack:
IP Function
---------------- --------------------------------------
0000aaaab48bba70 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x25d0
0000aaaab48bb618 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x2178
0000aaaab48bad1c std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x187c
0000ffff983957a0 <unknown>
0000ffff97c7e598 raise+0xb0
0000ffff97c7f974 abort+0x154
0000aaaab48bf60c std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x616c
0000aaaab49a9e54 std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::al
0000aaaab49a9bf0 std::_Rb_tree<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::pair<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const, std::__cxx11::basic_string<char, std::char_traits<char>, std::al
0000aaaab48ce358 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x14eb8
0000aaaab48cdf80 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x14ae0
0000aaaab497ce94 std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > std::operator+<char, std::char_traits<char>, std::allocator<char> >(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_
0000ffff93e89920 S_SbtUnimplementedInstruction+0x266ddc
0000ffff93ebad8c S_SbtUnimplementedInstruction+0x298248
0000ffff93eba800 S_SbtUnimplementedInstruction+0x297cbc
0000ffff93e79e88 S_SbtUnimplementedInstruction+0x257344
0000ffff93cb3858 S_SbtUnimplementedInstruction+0x90d14
0000ffff93cb49b4 S_SbtUnimplementedInstruction+0x91e70
0000ffff93cb4a84 S_SbtUnimplementedInstruction+0x91f40
0000ffff93c298d4 S_SbtUnimplementedInstruction+0x6d90
0000ffff93efc538 S_SbtUnimplementedInstruction+0x2d99f4
0000ffff8f2a64e0 S_SbtUnimplementedInstruction+0x5eb40
0000ffff8f2a5d78 S_SbtUnimplementedInstruction+0x5e3d8
Process: 26 - sqlservr
Thread: 153 (application thread 0x1f0)
Instance Id: abb90537-00a8-47c8-8e5d-cd67e117c35c
Crash Id: f1e6554d-c3ac-4c7b-8cbe-2bcc7361b712
Build stamp: 7e3b976a7614e3cb6d16ce08aa8e3b28924df7f1870dfe9956e396a15452340b
Distribution: Ubuntu 18.04.6 LTS aarch64 Processors: 16 Total Memory: 18832728064 bytes Timestamp: Sat Mar 29 10:54:41 2025 Last errno: 2 Last errno text: No such file or directory
