microsoft / mssql-docker

Official Microsoft repository for SQL Server in Docker resources
MIT License
1.72k stars 759 forks source link

Container don't run on Ubuntu #899

Open jkochen-exact opened 3 weeks ago

jkochen-exact commented 3 weeks ago

We have a dev server with 2017-CU13-ubuntu version on Ubuntu 22.04. in this week whe got this problem:

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

   Reason: 0x00000003
  Message: mappedBase == address

Stacktrace: 00005d1dd98abd55 00005d1dd98ac975 00005d1dd98ac580 00005d1dd9862c36 Process: 8 - sqlservr Thread: 78 (application thread 0x1108) Instance Id: 6cdd07ec-aed8-4438-84a5-c18121c34d1b Crash Id: 8e80c01b-cf02-456b-bd03-6adc766c78f6 Build stamp: 7d599fe53e35b5a1b0c8a5e4185d8b7334e01a8c5fa77540415502a85f37ef27 ` When I runned on my Windows Docker Desktop the docker runned ok...

I tried to run this command on both machines: docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=Password' -p 1400:1433 -d mcr.microsoft.com/mssql/server:2017-CU13-ubuntu

but, this occur only on versions < CU13, in the CU14 version work for us, but for any reason when I tried to run this version, and atach the databases in this versions, we get problems after restart VM because the container get errors to start too.

giautm commented 3 weeks ago

I've got the same issue here.

crynobone commented 3 weeks ago

Laravel Framework uses mcr.microsoft.com/mssql/server:2017-latest for SQL Server 2017 build and starting today it started to failed, see: https://github.com/laravel/framework/actions/runs/10931065047/job/30345266501

rkm commented 3 weeks ago

This surfaced for our project when the GitHub Actions ubuntu-22.04 CI image was updated from 20240908.1.0 to 20240915.1.0. We've upgraded to mcr.microsoft.com/mssql/server:2022-latest as a "workaround".

jkochen-exact commented 3 weeks ago

This problem occur for us when use ubuntu 22.04 and 24.04 on Azure, but on 20.04 work's fine. So we attach the data disk on other VM and are working for now.

GorlikItsMe commented 2 weeks ago

This problem occur for us when use ubuntu 22.04 and 24.04 on Azure, but on 20.04 work's fine. So we attach the data disk on other VM and are working for now.

Changing from

runs-on: ubuntu-latest

to

runs-on: ubuntu-20.04

in my github action really helped me. Thank you :heart: