-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Docker apple M1) Invalid mapping of address 0x40080f9000 in reserved address space below 0x400000000000 #668
Comments
Any luck? |
Unfortunately, no. |
I am also unable to connect to docker registry from my M1 Mac Air. I saw nobody is responding any solution to all these issue out there for new m1's |
Also having this issue and it's basically the main thing blocking my org from being able to use M1s for development. I'm setting up a remote Ubuntu Docker host at home for this but it'd be really wonderful if this was fixable, even if just in QEMU x86 emulated mode in Docker (although an ARM64 native container would be incredible) |
It has been more than a month and no one has a solution. Maybe it will get better with the next tech preview. |
Watching this space as well. |
Any news? |
An engineer from Docker said : The best alternatives today are to use Azure SQL Edge or other database technologies such as mariadb or mysql which are multi arch.
|
If Microsoft devotes resources to an ARM64 image, I will eat my hat :( |
Yes i went the Azure SQL Edge route and no issues for my purpose. https://hub.docker.com/_/microsoft-azure-sql-edge |
could you please help me installing it? Because after this step: "sudo docker run --cap-add SYS_PTRACE -e 'ACCEPT_EULA=1' -e 'MSSQL_SA_PASSWORD=yourStrong(!)Password' -p 1433:1433 --name azuresqledge -d mcr.microsoft.com/azure-sql-edge" nothing happens |
I can install azure without any problems. My current problem is to be able to install sql-server to run a Ruby on Rails application with sql-server as adapter |
running this command generates this result and it started on port 1433 |
Gave up on the Azure Edge image. Ran into the CLR error (I'd imagine quite a few DB's might depend on the CLR runtime). Saw Microsoft pulled CLR support for Azure Edge 4 years back due to a security risk and it never came back. |
Any progress on this? Azure SQL Edge works fine, but can't really use it due to lack of CLR support |
Same. I need CLR support. |
Same issue here, is there any work around for this? I have an older MacBook where I can run the container, how can I connect to the db server from my M1? Both computers are connected to the same network. Any help would be much appreciated! |
There’s no fix ATM until Microsoft fixes the image on their end. Won’t work with dockers preview that includes emulation for m1. Best you can do is the azure edge image which is ARM compatible but you lose things like CLR runtime. If you’re just doing simple stuff with small ish databases (I was learning with adventure works) you can pretty easily spin up a mssql server on the free google cloud tier and upload your database to a bucket there, whitelist the IP you’ll be connecting from and connect to it there. That’s what I ended up doing so I could continue my learning |
Any news? |
Azure SQL Edge works fine on my M1 Mac. |
Any news? |
I don't know if this helps this issue move at all, but I realized that building a custom image starting with Ubuntu 18.04 you will run into this problem as soon as you install sqlserver on it... |
@soccypowa Does it work if you use the image based on Ubuntu 16.04 (e.g. the tag |
@LuisBosquez @twright-msft @amvin87 Are you able to give us any insight on possible workarounds or an ETA for a possible fix? |
@thisisthekap Tried a few different starting points now, just for the "fun" of it, started with Ubuntu 16.04 and 18.04, tested both SQL 2107 and 2019, and to top it of I even built on CentOS 8 one last time... Still exits with the same error. I found a support article on MSFT about RHEL 7.4, it is the ball park of the same error, tried to, I am not very experienced with this, but to set the limits as pointed out in it, no success, SQL Server terminates and generates a core dump on RHEL 7.4 when you try to run mssql-conf. Even found this article that also is "kinda" the same MSSQL DOCKER ON UNRAID. Must be something it does that either is not allowed by the tech preview itself or the fact that we are virtualizing amd64 hardware and that there is some limitation of what Apple thinks is ok. |
There is a new RC released today, RC2, they have removed the preview banner at the bottom. Still though for our situation no cigar, tried both qemu and virtualization.framework, , official image as well as my custom build... |
I want to suggest a temporary workaround for this issue by using Azure SQL container. Here my docker-compose.yml config example: # Database instance
mssql:
image: mcr.microsoft.com/azure-sql-edge:latest
container_name: mssql
volumes:
- events_mssql:/var/opt/mssql
- ./setup.sql:/usr/config/setup.sql
ports:
- 1433:1433
environment:
- ACCEPT_EULA=Y
- MSSQL_SA_PASSWORD=Passw@rd
- MSSQL_PID=Developer
- MSSQL_DB=events_service
- MSSQL_USER=SA
- MSSQL_PASSWORD=Passw@rd
- MSSQL_DB_AUDIT_LOG=events_service_audit_log
volumes:
events_mssql: setup.sql file should be placed on the same level with the docker-compose.yml file CREATE DATABASE $(MSSQL_DB);
CREATE DATABASE $(MSSQL_DB_AUDIT_LOG);
GO
USE $(MSSQL_DB);
GO
CREATE LOGIN $(MSSQL_USER) WITH PASSWORD = '$(MSSQL_PASSWORD)';
GO
CREATE USER $(MSSQL_USER) FOR LOGIN $(MSSQL_USER);
GO
ALTER SERVER ROLE sysadmin ADD MEMBER [$(MSSQL_USER)];
GO Answer on StackOverflow: https://stackoverflow.com/questions/65398641/docker-connect-sql-server-container-non-zero-code-1/66919852#66919852 |
@kovalbogdan95 Thanks to the insights, |
@thisisthekap Sure, I'd rather run MSSQL container too, but for time being it's everything we got. |
I run both mcr.microsoft.com/mssql/server:2022-latest and mcr.microsoft.com/mssql/server:2019-latest images successfully on M1 macbook with "Use Rosetta for x86/amd64 emulation on Apple Silicon" feature enabled in Docker Desktop V4.19.0. |
Hi, I'm trying to run this on the latest versions: But enabling the rosetta option results in this log when running the container. 2023-05-17 15:33:31 -- Not first container startup -- Any ideas why? |
The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
* add v0 naming to tedious (mssql) * add v1 naming to tedious (mssql) * switch to a mostly working test sqlserver The standard mssql server image does not work on ARM [1]. Instead, we use `azure-sql-edge` [2], which provides a sufficient subset of mssql server API to test most of our integration. Unfortunately, this image does not support stored procedures [3], so tests related to these will still fail locally. [1] microsoft/mssql-docker#668 [2] https://hub.docker.com/_/microsoft-azure-sql-edge [3] https://learn.microsoft.com/en-us/azure/azure-sql-edge/features#unsupported-features
This work for me: version: '3.8'
services:
mssql:
image: mcr.microsoft.com/azure-sql-edge
environment:
- ACCEPT_EULA=Y
- SA_PASSWORD=Admin123@@
- MSSQL_PID=Developer
ports:
- 1433:1433
volumes:
- ./data:/var/opt/mssql |
Try this for Mac m1 docker run -e "ACCEPT_EULA=1" -e "MSSQL_SA_PASSWORD=reallyStrongPwd123" -e "MSSQL_PID=Developer" -e "MSSQL_USER=SA" -p 1433:1433 -d --name=sql mcr.microsoft.com/azure-sql-edge |
Thank you! You're a life saver |
Would this work on Ubuntu on RPI Arm64? |
I am seeing in Docker Desktop version 4.26.1 that the setting is out of experimental and in the general area.
|
Hello,
After I pulled the mcr.microsoft.com/mssql/server:latest image, I have a weird error when I want to launch it.
How can I resolve that ? Thank you in advance.
It seems to be the same problem in this SO question :
https://stackoverflow.com/questions/65398641/docker-connect-sql-server-container-non-zero-code-1
The text was updated successfully, but these errors were encountered: