SQL Server 2019 Linux docker bug

Question

SQL Server 2019 Linux docker bug

GuestMS 36

Hi,

I'm creating a docker image over the official SQL Server 2019 linux image (Express edition).
The process is quite simple and as follow:

pull the official MS linux image
docker pull mcr.microsoft.com/mssql/server:2019-latest)
run a docker container

docker run
--rm
-v <mypath_on_host>:<mypath_in_container>
--name sqlserver
-e "MSSQL_PID=Express"
-e "ACCEPT_EULA=Y"
-e "MSSQL_SA_PASSWORD=<my_super_password>"
-e "MSSQL_BACKUP_DIR=/var/opt/mssql/backup"
-e "MSSQL_MEMORY_LIMIT_MB=8192"
-p 1433:1433
-d mcr.microsoft.com/mssql/server:2019-latest

create an image from the container
docker commit -p sqlserver sqlserver-image
create a new container from the new image
docker run --name sqlserver2 -e "MSSQL_PID" -e "MSSQL_SA_PASSWORD" -p 5000:1433 -d sqlserver-image

Once the new container is running the following error message related to polybase is shown in the log:

2020-xx-xx xx:xx:xx.xx spid13s Error: 46906, Severity: 16, State: 1.
2020-xx-xx xx:xx:xx.xx spid13s Unable to retrieve registry value 'NodeRole' from Windows registry key 'Software\Microsoft\Microsoft SQL Server\MSSQL\Polybase\Configuration': (null).

First, Express edition does not support Polybase so why is it trying to configure it.
Second the error message is related to Windows registry but I'm running a linux container....!!!

Any idea as to what this is related ?
It really looks like a bug...

Thanks.

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2020-10-12T20:28:20.757+00:00

Beside from the fact that the error might look a little ugly, is there any actual damage? Does it prevent things from working?
GuestMS 36 Reputation points

2020-10-12T21:43:28.187+00:00

HI Erland,

Thanks for asking this is precisely the issue i'm struggling with.

We cannot conduct thorough testing of the product (must be done by ms) and even we did it we still won't have the guarantee there is no or will be no side effect.

Going for prod deployment with a buggy product is not very safe (though Polybase is à separate service).

Any similar experience with the linux docker version ?

BR.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2020-10-12T22:13:32.677+00:00

I'm still not sure that I get this, but if you think this is a blocking issue that prevents you from going into production, you would need to open a support case with Microsoft to get a fix.

However, unless you are actually experiencing any problems, I would expect them to tell you that the error message is benign and can be ignored.

I have only played with Docker a little bit. But I tried to create an container from the CU8 image,. I see the same messages as you in the errorlog. But apart from that the instance seems to work, and I was able to create a few databases.

Accepted answer

3 additional answers

Your answer

Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2020-10-12T20:28:20.757+00:00

Beside from the fact that the error might look a little ugly, is there any actual damage? Does it prevent things from working?
GuestMS 36 Reputation points

2020-10-12T21:43:28.187+00:00

HI Erland,

Thanks for asking this is precisely the issue i'm struggling with.

We cannot conduct thorough testing of the product (must be done by ms) and even we did it we still won't have the guarantee there is no or will be no side effect.

Going for prod deployment with a buggy product is not very safe (though Polybase is à separate service).

Any similar experience with the linux docker version ?

BR.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2020-10-12T22:13:32.677+00:00

I'm still not sure that I get this, but if you think this is a blocking issue that prevents you from going into production, you would need to open a support case with Microsoft to get a fix.

However, unless you are actually experiencing any problems, I would expect them to tell you that the error message is benign and can be ignored.

I have only played with Docker a little bit. But I tried to create an container from the CU8 image,. I see the same messages as you in the errorlog. But apart from that the instance seems to work, and I was able to create a few databases.

Answer 1

m 4,276

Hi @GuestMS ,

If you are sure this is one bug, I recommend you to submit your issue to the Microsoft feedback at this link : https://feedback.azure.com/forums/908035-sql-server .
This site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft feedback.

BR,
Mia

If the answer is helpful, please click "Accept Answer" and upvote it.

Nate Miller 1 Reputation point

2020-12-17T04:49:40.643+00:00
I had the same problem. Wasted a bunch of time trying to figure out why my developer licensed server stopped allowing me to connect.
I finally saw this and found the same error message about a windows registry entry on Linux.
I downgraded the mssql-server version and everything works now.

I downgraded with the following command:

apt install mssql-server=15.0.4043.16-4 systemctl restart mssql-server

Answer 2

GuestMS 36

Hi Mia,

It's definitely a bug that was introduced with CU8 of SQL Server 2019 (and thus also existing in the image with the latest tag).

Indeed, I've tried to use the "Developer" edition and the error message appears as well in the log of SQL Server.
But the message does not show up with CU6, nor with the Global Availability image.

As a side note, all official images of SQL Server 2019 on DockerHub are built with Ubuntu 16.04.
I'm not building linux docker from scratch (issues with OpenSSL version).

Regards.

Ian Fuller 1 Reputation point

2021-01-28T19:21:23.947+00:00

It's definitely a bug that was introduced with CU8 of SQL Server 2019

Do you have any official post/link/documentation to confirm this?

Answer 3

Hi @GuestMS ,

First, Express edition does not support Polybase so why is it trying to configure it.
Second the error message is related to Windows registry but I'm running a linux container....!!!
Any idea as to what this is related ?

What is your linux OS? Please install the SQL2019 developer and the latest CU to test again.

Quote from this doc.: quickstart-install-connect-docker:

...
Starting with SQL Server 2019 CU3, Ubuntu 18.04 is supported.
...

By default, this creates a container with the Developer edition of SQL Server 2019.
...

BR,
Mia

If the answer is helpful, please click "Accept Answer" and upvote it.

Answer 4

Ivan Carrazana 1

Hi

I had the same error log when doing a step-by-step installation on RH8. I solved it by installing the mssql-server-polybase package. I have no experience with containers but this is the way to not see that log error anymore

Regards

Share via

SQL Server 2019 Linux docker bug

3 additional answers

Your answer