-
Notifications
You must be signed in to change notification settings - Fork 282
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
cant connection to SQL Server from dockerized net6.0 app #1446
Comments
@JRahnama Hi, im will waiting ofcourse for patch. Additional Im trying with
and ConnString as ... ;Encrypt=False; or TrustServerCertificate=True - the same effect : the POD crash Regards |
@ch0mik are you using Kerberos for authentication? |
@JRahnama yes, Im use Kerberos for Auth as SideCar and shared folder for sharing token file see the stack trace above. Regards |
it is more similar to #1390. There is an issue with dotnet run time issue. Our hot fix release is scheduled around mid January. |
@JRahnama hi!, i found that fix has been released : https://github.com/dotnet/runtime/releases/tag/v6.0.1 fix : 85ed860 has been merged |
Does the fix work in your case? |
|
Sounds like this is related to #1402 |
@JRahnama i think the problem back with 6.0.2 runtime ... |
only works the workaround
...
|
In my case, I was running All connections failed with
From SQL logs, it turned out the problem was with the mounted volumes: By not mounting Docker volumes, I could connect. So the original error message threw me off in the wrong direction, debugging SSL and TLS1.2. Maybe this helps some others googling this. |
Hi. Any update? |
with newest Microsoft.Data.SqlClient or 3.0.1 the same on net6.0 docker image (RedHat UBI : redhat-registry.artifactory.mbank.pl/ubi8/dotnet-60-runtime ) and compiled as targetFramework = net6.0
but the same code, but 3.1 runtime from RedHat UBI and compiled as targetFramework = .net core 3.1 works fine with newest Microsoft.Data.SqlClient
I see thats on Debian`s images is the same : #1436
similar case : #1402
The text was updated successfully, but these errors were encountered: