Last active
April 13, 2025 08:06
-
-
Save jjuanrivvera99/e4357795b5f9ba239533fbd849bd008e to your computer and use it in GitHub Desktop.
SQL Server with Docker Compose
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| version: '3.3' | |
| services: | |
| mssql: | |
| container_name: sql-server | |
| image: mcr.microsoft.com/mssql/server:2017-latest | |
| #image: mcr.microsoft.com/mssql/server:2017-CU11-ubuntu | |
| restart: always | |
| environment: | |
| ACCEPT_EULA: "Y" | |
| SA_PASSWORD: "Contraseña12345678" | |
| ports: | |
| - 1433:1433 | |
| volumes: | |
| - my-volume:/var/opt/mssql | |
| volumes: | |
| my-volume: |
This program has encountered a fatal error and cannot continue running
This program has encountered a fatal error and cannot continue running
Hi Halida!
Although this is a 5-year-old example, I just tested it from scratch on a Manjaro Linux machine and it worked perfectly:
Could you provide more details on how to reproduce the problem?
Then I can see if I can be of help or not.
I'm runing ubuntu 24.04 on dell precision 5520,
$ docker --version
Docker version 26.1.3, build b72abbb
$ docker compose up
[+] Running 4/4
✔ mssql Pulled 54.5s
✔ 699451820735 Pull complete 9.7s
✔ 861e6e6e8e5e Pull complete 49.4s
✔ 4403d783b046 Pull complete 52.0s
[+] Running 3/3
✔ Network testdb_default Created 0.2s
✔ Volume "testdb_my-volume" Created 0.0s
✔ Container sql-server Created 1.1s
Attaching to sql-server
sql-server | SQL Server 2017 will run as non-root by default.
sql-server | This container is running as user root.
sql-server | To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
sql-server | This program has encountered a fatal error and cannot continue running at Fri May 31 15:25:14 2024
sql-server | The following diagnostic information is available:
sql-server |
sql-server | Reason: 0x00000001
sql-server | Signal: SIGABRT - Aborted (6)
sql-server | Stack:
sql-server | IP Function
sql-server | ---------------- --------------------------------------
sql-server | 00005e921e18b9ec <unknown>
sql-server | 00005e921e18b432 <unknown>
sql-server | 00005e921e18aa41 <unknown>
sql-server | 00007a1178426f10 killpg+0x40
sql-server | 00007a1178426e87 gsignal+0xc7
sql-server | 00007a11784287f1 abort+0x141
sql-server | 00005e921e11f672 <unknown>
sql-server | 00005e921e1a2204 <unknown>
sql-server | 00005e921e1d51f8 <unknown>
sql-server | 00005e921e1d4fda <unknown>
sql-server | 00005e921e12b4ea <unknown>
sql-server | 00005e921e12b13f <unknown>
sql-server | Process: 9 - sqlservr
sql-server | Thread: 80 (application thread 0x134)
sql-server | Instance Id: 6123dd35-a36e-406c-bf52-f248ba1d68a4
sql-server | Crash Id: 18a90aad-0492-4904-9789-537b53ba5ee3
sql-server | Build stamp: 388f6c66c6dbc4da12ba35a003fcb9b5e0f65b6bc460dbf45ba9cf2562768e67
sql-server | Distribution: Ubuntu 18.04.6 LTS
sql-server | Processors: 8
sql-server | Total Memory: 33243959296 bytes
sql-server | Timestamp: Fri May 31 15:25:14 2024
sql-server | Last errno: 2
sql-server | Last errno text: No such file or directory
sql-server | Capturing a dump of 9
sql-server | Successfully captured dump: /var/opt/mssql/log/core.sqlservr.5_31_2024_15_25_14.9
sql-server | Executing: /opt/mssql/bin/handle-crash.sh with parameters
sql-server | handle-crash.sh
sql-server | /opt/mssql/bin/sqlservr
sql-server | 9
sql-server | /opt/mssql/bin
sql-server | /var/opt/mssql/log/
sql-server |
sql-server | 6123dd35-a36e-406c-bf52-f248ba1d68a4
sql-server | 18a90aad-0492-4904-9789-537b53ba5ee3
sql-server |
sql-server | /var/opt/mssql/log/core.sqlservr.5_31_2024_15_25_14.9
sql-server |
sql-server | Ubuntu 18.04.6 LTS
sql-server | Capturing core dump and information to /var/opt/mssql/log...
sql-server | dmesg: read kernel buffer failed: Operation not permitted
sql-server | /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
sql-server | /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
sql-server | Fri May 31 15:25:17 UTC 2024 Capturing program information
sql-server | Dump already generated: /var/opt/mssql/log/core.sqlservr.5_31_2024_15_25_14.9, moving to /var/opt/mssql/log/core.sqlservr.9.temp/core.sqlservr.9.gdmp
sql-server | Moving logs to /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log
sql-server | Fri May 31 15:25:17 UTC 2024 Capturing program binaries
sql-server | Fri May 31 15:25:18 UTC 2024 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.05_31_2024_15_25_15.9.d
sql-server exited with code 0
I guess it is ubuntu 24.04 issue, rollback to 22.04 should work.
same problem, same versions.
going back to 22.04 is not an option for long, because we're in the middle of a datacenter-wide migration to 24 and this is a road block. we should bring this to the attention Microsoft. I'll have a look if there is already a support case open.
microsoft/mssql-docker#881 Here are some versions works.
after add this option, work, but this developer mode
MSSQL_PID: "Developer"
version: '3.3'
services:
mssql:
container_name: sql-server
image: mcr.microsoft.com/mssql/server:2017-latest
restart: always
environment:
ACCEPT_EULA: "Y"
SA_PASSWORD: "YourStrong!Passw0rd"
MSSQL_LOGGING: "verbose"
MSSQL_PID: "Developer"
ports:
- 1433:1433
volumes:
- ./data:/var/opt/mssql/data
- ./3:/backup
deploy:
resources:
limits:
cpus: '2'
memory: 4G
This has something to do with the license plan. Admittedly, the name 'MSSQL_PID' is an unfortunate choice by Microsoft. But that's how we know it.
You can see the valid values here:
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
mersi