I am using Docker and the container using docker compose fails with:
This program has encountered a fatal error and cannot continue running at Sat May 25 17:23:28 2024
The following diagnostic information is available:
```
Reason: 0x00000001
Signal: SIGABRT - Aborted (6)
Stack:
IP Function
Below is the full logs i recieved
[+] Running 1/0
✔ Container securebank-securebank-1 Created 0.0s
Attaching to securebank-1
securebank-1 | MailDev webapp running at http://0.0.0.0:1080
securebank-1 | MailDev SMTP Server running at 0.0.0.0:1025
securebank-1 | 2024-05-25 17:23:27.03 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
2024-05-25 17:23:27.12 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
2024-05-25 17:23:27.13 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
2024-05-25 17:23:27.16 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
2024-05-25 17:23:27.33 Server Microsoft SQL Server 2019 (RTM-CU3) (KB4538853) - 15.0.4023.6 (X64)
securebaMar 4 2020 00:59:26
securebaCopyright (C) 2019 Microsoft Corporation
securebaDeveloper Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2024-05-25 17:23:27.34 Server UTC adjustment: 0:00
2024-05-25 17:23:27.34 Server (c) Microsoft Corporation.
2024-05-25 17:23:27.34 Server All rights reserved.
2024-05-25 17:23:27.34 Server Server process ID is 44.
2024-05-25 17:23:27.34 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2024-05-25 17:23:27.34 Server Registry startup parameters:
secureba -d /var/opt/mssql/data/master.mdf
secureba -l /var/opt/mssql/data/mastlog.ldf
secureba -e /var/opt/mssql/log/errorlog
2024-05-25 17:23:27.35 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-05-25 17:23:27.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-05-25 17:23:27.36 Server Detected 12408 MB of RAM. This is an informational message; no user action is required.
2024-05-25 17:23:27.36 Server Using conventional memory in the memory manager.
2024-05-25 17:23:27.45 Server Page exclusion bitmap is enabled.
2024-05-25 17:23:27.51 Server Buffer pool extension is not supported on Linux platform.
2024-05-25 17:23:27.51 Server Buffer Pool: Allocating 262144 bytes for 207478 hashPages.
2024-05-25 17:23:27.83 Server Buffer pool extension is already disabled. No action is necessary.
2024-05-25 17:23:28.41 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-05-25 17:23:28.47 Server Query Store settings initialized with enabled = 1,
2024-05-25 17:23:28.50 Server The maximum number of dedicated administrator connections for this instance is '1'
2024-05-25 17:23:28.51 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-05-25 17:23:28.52 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-05-25 17:23:28.54 Server In-Memory OLTP initialized on lowend machine.
2024-05-25 17:23:28.66 Server [INFO] Created Extended Events session 'hkenginexesession'
2024-05-25 17:23:28.66 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-05-25 17:23:28.67 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2024-05-25 17:23:28.68 Server clflushopt is selected for pmem flush operation.
2024-05-25 17:23:28.69 Server Software Usage Metrics is disabled.
2024-05-25 17:23:28.70 spid10s [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2024-05-25 17:23:28.71 spid10s Starting up database 'master'.
2024-05-25 17:23:28.78 Server CLR version v4.0.30319 loaded.
securebank-1 | This program has encountered a fatal error and cannot continue running at Sat May 25 17:23:28 2024
securebank-1 | The following diagnostic information is available:
securebank-1 |
securebank-1 | Reason: 0x00000001
securebank-1 | Signal: SIGABRT - Aborted (6)
securebank-1 | Stack:
securebank-1 | IP Function
securebank-1 | ---------------- --------------------------------------
securebank-1 | 000064baf6168803
securebank-1 | 000064baf61682de
securebank-1 | 000064baf61672ba
securebank-1 | 00007f56dd92b4b0 killpg+0x40
securebank-1 | 00007f56dd92b428 gsignal+0x38
securebank-1 | 00007f56dd92d02a abort+0x16a
securebank-1 | 000064baf61b8406
securebank-1 | Process: 26 - sqlservr
securebank-1 | Thread: 137 (application thread 0x1b0)
securebank-1 | Instance Id: af1462e4-c72a-439c-967f-759f32cf040f
securebank-1 | Crash Id: 8b955ec3-554e-4846-9243-f1351ee2bcd7
securebank-1 | Build stamp: 555e778ef189c2ebddb845f143a741b4975200e2130969e77e51f72ff7ec0476
securebank-1 | Distribution: Ubuntu 16.04.6 LTS
securebank-1 | Processors: 8
securebank-1 | Total Memory: 16263729152 bytes
securebank-1 | Timestamp: Sat May 25 17:23:28 2024
securebank-1 | Last errno: 2
securebank-1 | Last errno text: No such file or directory
securebank-1 |
securebank-1 | Ubuntu 16.04.6 LTS
securebank-1 | Capturing core dump and information to /var/opt/mssql/log...
securebank-1 | dmesg: read kernel buffer failed: Operation not permitted
securebank-1 | No journal files were found.
securebank-1 | No journal files were found.
securebank-1 | Sat May 25 17:23:30 UTC 2024 Capturing program information
securebank-1 | Sat May 25 17:23:30 UTC 2024 Attempting to capture a dump with paldumper for pid 26
securebank-1 | WARNING: Capture attempt failure detected
securebank-1 | Attempting to capture a filtered dump with paldumper for pid 26
securebank-1 | WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.26.temp/log/paldumper-debug.log for details
securebank-1 | Sat May 25 17:23:30 UTC 2024 Attempting to capture a dump with gdb
securebank-1 | Sat May 25 17:23:30 UTC 2024 Captured a dump with gdb
securebank-1 | Sat May 25 17:23:30 UTC 2024 Capturing program binaries
securebank-1 | Sat May 25 17:23:31 UTC 2024 Compressing the dump files
securebank-1 exited with code 1
I am using Docker and the container using docker compose fails with:
This program has encountered a fatal error and cannot continue running at Sat May 25 17:23:28 2024 The following diagnostic information is available:
Reason: 0x00000001 Signal: SIGABRT - Aborted (6) Stack: IP Function
[+] Running 1/0 ✔ Container securebank-securebank-1 Created 0.0s Attaching to securebank-1 securebank-1 | MailDev webapp running at http://0.0.0.0:1080 securebank-1 | MailDev SMTP Server running at 0.0.0.0:1025 securebank-1 | 2024-05-25 17:23:27.03 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'. 2024-05-25 17:23:27.12 Server Setup step is FORCE copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'. 2024-05-25 17:23:27.13 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'. 2024-05-25 17:23:27.16 Server Setup step is FORCE copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'. 2024-05-25 17:23:27.33 Server Microsoft SQL Server 2019 (RTM-CU3) (KB4538853) - 15.0.4023.6 (X64) securebaMar 4 2020 00:59:26 securebaCopyright (C) 2019 Microsoft Corporation securebaDeveloper Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2024-05-25 17:23:27.34 Server UTC adjustment: 0:00
2024-05-25 17:23:27.34 Server (c) Microsoft Corporation.
2024-05-25 17:23:27.34 Server All rights reserved.
2024-05-25 17:23:27.34 Server Server process ID is 44.
2024-05-25 17:23:27.34 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2024-05-25 17:23:27.34 Server Registry startup parameters:
secureba -d /var/opt/mssql/data/master.mdf
secureba -l /var/opt/mssql/data/mastlog.ldf
secureba -e /var/opt/mssql/log/errorlog
2024-05-25 17:23:27.35 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2024-05-25 17:23:27.36 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-05-25 17:23:27.36 Server Detected 12408 MB of RAM. This is an informational message; no user action is required.
2024-05-25 17:23:27.36 Server Using conventional memory in the memory manager.
2024-05-25 17:23:27.45 Server Page exclusion bitmap is enabled.
2024-05-25 17:23:27.51 Server Buffer pool extension is not supported on Linux platform.
2024-05-25 17:23:27.51 Server Buffer Pool: Allocating 262144 bytes for 207478 hashPages.
2024-05-25 17:23:27.83 Server Buffer pool extension is already disabled. No action is necessary.
2024-05-25 17:23:28.41 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-05-25 17:23:28.47 Server Query Store settings initialized with enabled = 1,
2024-05-25 17:23:28.50 Server The maximum number of dedicated administrator connections for this instance is '1'
2024-05-25 17:23:28.51 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-05-25 17:23:28.52 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-05-25 17:23:28.54 Server In-Memory OLTP initialized on lowend machine.
2024-05-25 17:23:28.66 Server [INFO] Created Extended Events session 'hkenginexesession'
2024-05-25 17:23:28.66 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-05-25 17:23:28.67 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2024-05-25 17:23:28.68 Server clflushopt is selected for pmem flush operation.
2024-05-25 17:23:28.69 Server Software Usage Metrics is disabled.
2024-05-25 17:23:28.70 spid10s [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2024-05-25 17:23:28.71 spid10s Starting up database 'master'.
2024-05-25 17:23:28.78 Server CLR version v4.0.30319 loaded.
securebank-1 | This program has encountered a fatal error and cannot continue running at Sat May 25 17:23:28 2024
securebank-1 | The following diagnostic information is available:
securebank-1 |
securebank-1 | Reason: 0x00000001
securebank-1 | Signal: SIGABRT - Aborted (6)
securebank-1 | Stack:
securebank-1 | IP Function
securebank-1 | ---------------- --------------------------------------
securebank-1 | 000064baf6168803
securebank-1 | 000064baf61682de
securebank-1 | 000064baf61672ba
securebank-1 | 00007f56dd92b4b0 killpg+0x40
securebank-1 | 00007f56dd92b428 gsignal+0x38
securebank-1 | 00007f56dd92d02a abort+0x16a
securebank-1 | 000064baf61b8406
securebank-1 | Process: 26 - sqlservr
securebank-1 | Thread: 137 (application thread 0x1b0)
securebank-1 | Instance Id: af1462e4-c72a-439c-967f-759f32cf040f
securebank-1 | Crash Id: 8b955ec3-554e-4846-9243-f1351ee2bcd7
securebank-1 | Build stamp: 555e778ef189c2ebddb845f143a741b4975200e2130969e77e51f72ff7ec0476
securebank-1 | Distribution: Ubuntu 16.04.6 LTS
securebank-1 | Processors: 8
securebank-1 | Total Memory: 16263729152 bytes
securebank-1 | Timestamp: Sat May 25 17:23:28 2024
securebank-1 | Last errno: 2
securebank-1 | Last errno text: No such file or directory
securebank-1 |
securebank-1 | Ubuntu 16.04.6 LTS
securebank-1 | Capturing core dump and information to /var/opt/mssql/log...
securebank-1 | dmesg: read kernel buffer failed: Operation not permitted
securebank-1 | No journal files were found.
securebank-1 | No journal files were found.
securebank-1 | Sat May 25 17:23:30 UTC 2024 Capturing program information
securebank-1 | Sat May 25 17:23:30 UTC 2024 Attempting to capture a dump with paldumper for pid 26
securebank-1 | WARNING: Capture attempt failure detected
securebank-1 | Attempting to capture a filtered dump with paldumper for pid 26
securebank-1 | WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.26.temp/log/paldumper-debug.log for details
securebank-1 | Sat May 25 17:23:30 UTC 2024 Attempting to capture a dump with gdb
securebank-1 | Sat May 25 17:23:30 UTC 2024 Captured a dump with gdb
securebank-1 | Sat May 25 17:23:30 UTC 2024 Capturing program binaries
securebank-1 | Sat May 25 17:23:31 UTC 2024 Compressing the dump files
securebank-1 exited with code 1