Open Roberto-Neto opened 1 month ago
I'm also experiencing this issue (as with a number of my colleagues).
docker compose up -d
The docker-compose
file uses an image based on https://hub.docker.com/r/microsoft/mssql-server's 2019-latest
tag.
I've attached a (shortened) log file from the compose up
command. There's a section where it repeats ~200 lines with a different /proc/10/task/####
value that I've removed for brevity.
Highlighting the diagnostics I received, as they are a bit more details than the above:
2024-07-29 14:45:42.65 spid30s Starting up database 'master'.
This program has encountered a fatal error and cannot continue running at Mon Jul 29 14:45:42 2024
The following diagnostic information is available:
Reason: 0x00000001
Signal: SIGABRT - Aborted (6)
Stack:
IP Function
---------------- --------------------------------------
00005555556a1c71 std::__1::bad_function_call::~bad_function_call()+0x29f81
00005555556a1636 std::__1::bad_function_call::~bad_function_call()+0x29946
00005555556a0bbf std::__1::bad_function_call::~bad_function_call()+0x28ecf
00007fffff107090 killpg+0x40
00007fffff10700b gsignal+0xcb
00007fffff0e6859 abort+0x12b
000055555563d426 std::__1::basic_stringbuf<char, std::__1::char_traits<char>, std::__1::allocator<char>>::str() const+0xd736
Process: 10 - sqlservr
Thread: 145 (application thread 0x238)
Instance Id: a266616a-c91a-4a7f-a99d-f3dc16d3e830
Crash Id: 495475a2-1f39-4e77-bfb8-c0f59d6d024e
Build stamp: 51e51a4dfa4635df0a9847dbd15101717167582ccfb61f8ace2ffc3b0924d54d
Distribution: Ubuntu 20.04.6 LTS
Processors: 10
Total Memory: 8219537408 bytes
Timestamp: Mon Jul 29 14:45:42 2024
Last errno: 2
docker version
Client: Docker Engine - Community
Version: 27.1.1
API version: 1.46
Go version: go1.22.5
Git commit: 63125853e3
Built: Fri Jul 19 17:35:01 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Server: Docker Desktop 4.33.0 (160616)
Engine:
Version: 27.1.1
API version: 1.46 (minimum version 1.24)
Go version: go1.21.12
Git commit: cc13f95
Built: Tue Jul 23 19:57:14 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.19
GitCommit: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc:
Version: 1.7.19
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client: Docker Engine - Community
Version: 27.1.1
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.16.1-desktop.1
Path: /Users/$USER/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.1-desktop.1
Path: /Users/$USER/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.34
Path: /Users/$USER/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.14
Path: /Users/$USER/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/$USER/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.25
Path: /Users/$USER/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/$USER/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: /Users/$USER/.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/$USER/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.11.0
Path: /Users/$USER/.docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 11
Server Version: 27.1.1
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: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.10.0-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 10
Total Memory: 7.655GiB
Name: docker-desktop
ID: 0bebe745-5bac-45b5-b335-162c8ad607cb
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/$USER/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
Let me know if there's any other information that would be helpful. I've downgraded to 4.32.0 for now.
Also with mcr.microsoft.com/mssql/server:2017-CU31-ubuntu-18.04 and macOS 14.5 (Apple M2 Max).
Hello Andreas
I cannot agree with you that I have to use this version of the SQL 2017 image. With the previous version of Docker, everything worked, but I have been using Docker for a while and the image stopped working after the version upgrade. I even have an image of SQL Edge that no longer works. I have other SQL images (2019/2022), and they work perfectly even after the Upgrade.
Best regards
Andreas Ernst @.***> escreveu (terça, 30/07/2024 à(s) 09:43):
Also with mcr.microsoft.com/mssql/server:2017-CU31-ubuntu-18.04 and macOS 14.5 (Apple M2 Max).
— Reply to this email directly, view it on GitHub https://github.com/docker/for-mac/issues/7368#issuecomment-2257805302, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQJJKCZXE46YUBQ3TZ2LM3ZO5G43AVCNFSM6AAAAABLUBSZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXHAYDKMZQGI . You are receiving this because you authored the thread.Message ID: @.***>
Hi Roberto,
i have to use this versions, because our customer uses this version of MS SQL. I downgraded to 4.32.0.
Best regards Andreas
Hi Andreas
With 4.32.0, everything works. Thank you very much.
Best regards Roberto
Andreas Ernst @.***> escreveu (terça, 30/07/2024 à(s) 10:14):
Hi Roberto,
i have to use this versions, because our customer uses this version of MS SQL. I downgraded to 4.32.0.
Best regards Andreas
— Reply to this email directly, view it on GitHub https://github.com/docker/for-mac/issues/7368#issuecomment-2257870286, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQJJKGHLRL4YLVSRVOPLBTZO5KQBAVCNFSM6AAAAABLUBSZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXHA3TAMRYGY . You are receiving this because you authored the thread.Message ID: @.***>
I'm experiencing this with mcr.microsoft.com/azure-sql-edge
as well. Downgrading to 4.32.0 fixed the issue.
Also had this issue last week running Sonoma 14.5 on M1 Max. An old mcr.microsoft.com/azure-sql-edge image acted up and I wasn't able to access several management features anymore. Setting up a new container failed completely, downgraded to 4.32.0.
Got this issue with SQL 2017 image also. Downgraded for now.
Having this issue too 👍
Sonoma 14.6 Docker Desktop v.4.33.0
happening to mssql 2017 image.
Hi Brian
With update 4.0.33, SQL 2017 only worked after several START attempts. But stop . SQL Edge has stopped working.
Note: I have my SQL instances to start manually to save resources. I start in the instance I want to work on. With 4.0.32 everything works... I'm using docker every days in my projects.
SQL 2017 Log below
2024-08-06 11:40:27 000055555569e9ec
2024-08-06 11:38:28 0000aaaab39dba70
std::_Sp_counted_base<(gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x25d0
2024-08-06 11:38:28 0000aaaab39db618
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x2178
2024-08-06 11:38:28 0000aaaab39dad1c
std::_Sp_counted_base<(gnu_cxx::_Lock_policy)2>::~_Sp_counted_base()+0x187c
2024-08-06 11:38:28 0000ffff81f2c7a0
[image: image.png]
[image: image.png] [image: image.png]
Brian Chew @.***> escreveu (terça, 6/08/2024 à(s) 07:59):
Having this issue too 👍
— Reply to this email directly, view it on GitHub https://github.com/docker/for-mac/issues/7368#issuecomment-2270526803, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANQJJKBJWJDN7A4D2UTVWYLZQBX6JAVCNFSM6AAAAABLUBSZ5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZQGUZDMOBQGM . You are receiving this because you authored the thread.Message ID: @.***>
@Roberto-Neto Maybe consider renaming the issue to something like '4.33.0 breaks containers like MSSQL'.
I'm also experiencing this issue with 4.33.0 breaking my mssql container.
2024-08-06 13:15:43 2024/08/06 18:15:43 [launchpadd] WARNING: Failed to load /var/opt/mssql/mssql.conf ini file with error open /var/opt/mssql/mssql.conf: no such file or directory
2024-08-06 13:15:43 2024/08/06 18:15:43 [launchpadd] INFO: DataDirectories = /bin:/etc:/lib:/lib32:/lib64:/sbin:/usr/bin:/usr/include:/usr/lib:/usr/lib32:/usr/lib64:/usr/libexec/gcc:/usr/sbin:/usr/share:/var/lib:/opt/microsoft:/opt/mssql-extensibility:/opt/mssql/mlservices:/opt/mssql/lib/zulu-jre-11:/opt/mssql-tools
2024-08-06 13:15:43 2024/08/06 18:15:43 Drop permitted effective capabilities.
2024-08-06 13:15:43 2024/08/06 18:15:43 [launchpadd] INFO: Polybase remote hadoop bridge disabled
2024-08-06 13:15:43 2024/08/06 18:15:43 [launchpadd] INFO: Launchpadd is connecting to mssql on localhost:1431
2024-08-06 13:15:43 2024/08/06 18:15:43 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-08-06 13:15:44 2024/08/06 18:15:44 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-08-06 13:15:45 2024/08/06 18:15:45 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-08-06 13:15:46 2024/08/06 18:15:46 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-08-06 13:15:47 2024/08/06 18:15:47 [launchpadd] WARNING: Failed to connect to SQL because: dial tcp [::1]:1431: connect: connection refused, will reattempt connection.
2024-08-06 13:15:49 This program has encountered a fatal error and cannot continue running at Tue Aug 6 18:15:49 2024
How does one Downgrade to 4.32.0?
@caseyhelbling Simply delete the Docker.app from Applications folder and install 4.32.0 after downloading from the releases section: https://docs.docker.com/desktop/release-notes/
Hi there,
the source of the issue is a known bugin mssql-server-docker
that causes mssql-server fail with the symptoms you are describing when running on Linux kernels 6.7 and later.
Docker Desktop 4.33 ships with Linux Kernel 6.10, while Docker Desktop 4.32 is on kernel 6.6.
Microsoft has fixed the bug on mcr.microsoft.com/mssql/server
starting from tag 2022-CU11-ubuntu-22.04
(and 2022-latest
), but the fix appears not to have been backported to 2017-*
tags.
Workarounds are to either upgrade your mssql/server
image to 2022-latest
or downgrade Docker Desktop to 4.32 (in order to use an older linux kernel).
The bug also affects azure-sql-edge
images, which run MSSQL
. Unfortunately, the images currently published by Microsoft do not seem to include the fix to support kernels 6.7 and later.
In this case, the only possible workaround until Microsoft updates the images is to downgrade Docker Desktop to 4.32.
I have opened an issue with Microsoft to make them aware of the problem. Please, feel free to follow that issue to track progress.
azure-sql-edge does no longer support Apple Silicon, see https://techcommunity.microsoft.com/t5/sql-server-blog/azure-sql-edge-update-september-2023/ba-p/3930827
Good news: Docker for Mac includes virtualization for AMD images (under Settings > General), so it's possible to use the image mcr.microsoft.com/mssql/server:2022-latest which includes the fix for the newer linux kernels.
See also https://www.justinjbird.me/blog/2024/running-sql-server-on-macos-using-docker/
Same issue and logs here using SQL Edge image from an Apple M1 chip. Downgrading to 4.32.0 worked, hope this will get fixed on the next release
Update: Moved to mcr.microsoft.com/mssql/server:2022-latest
. Some config is needed when running on Docker Compose:
user: root
platform: linux/amd64 # Required since the base image uses a different platform (Docker Virtualization)
Description
With the new Update V.4.33., the Vms started but after a few seconds, they stopped.
Reproduce
1 - Go to Dashboard 2- Start VM
Expected behavior
No response
docker version
docker info
Diagnostics ID
2CC47E7A-01A1-406D-ABB8-461FE9D0521F/20240729111206
Additional Info
No response