Skip to main content

Dockerize a dotnet core application with SQL connectivity


Before reading this article, I am assuming that you know Docker, Dotnet core and have a dotnet core application which is trying to connect to SQL server. Read how to build aspnet core app, docker and run the docker container.

If docker container is running and you are not able to connect to database, this blog should help you fix it. 

Prerequisite - 
  • Make sure code is working via running aspnet core locally via visual studio or command line.
  • Port 1433 is opened for connecting to SQL server.

Solution

If you have Docker file ready, it should somewhat look like below file - 

FROM
mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
WORKDIR /app

# Copy csproj and restore as distinct layers
COPY /SampleAPI/*.csproj ./
RUN dotnet restore

# Copy everything else and build
COPY . .
WORKDIR /app/SampleAPI
RUN dotnet publish -c Production -o publish

# Build runtime image
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1

WORKDIR /app/SampleAPI
COPY --from=build-env /app/SampleAPI .
WORKDIR /app/SampleAPI/bin/Production/netcoreapp3.1

ENTRYPOINT ["dotnet", "SampleAPI.dll"]



Add following lines to make database connectivity  

#To connect to database
RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf
RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /usr/lib/ssl/openssl.cnf
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /usr/lib/ssl/openssl.cnf

The above lines invoke 'sed'(stream Editor) to open file and edit it. 
  • Line 1 is modfying '/etc/ssl/openssl.conf' file and replacing MinProtocal = TLSv1.2 to MinProtocol = TLSv1. 
  • Line 2 is modifying same protocol in another file. 
  • Line 3 is setting the security level from DEFAULT@SECLEVEL=2 to DEFAULT@SECLEVEL=1. 
  • Line 4 is modifying the same in another file.
Note: You can add first 2 OR last 2 OR all lines depending upon connection issue with database.

Final Docker file will look something like that - 
FROM mcr.microsoft.com/dotnet/core/sdk:3.1 AS build-env
WORKDIR /app

# Copy csproj and restore as distinct layers
COPY /SampleAPI/*.csproj ./
RUN dotnet restore

# Copy everything else and build
COPY . .
WORKDIR /app/SampleAPI
RUN dotnet publish -c Production -o publish

# Build runtime image
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1

#To connect to database
RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /etc/ssl/openssl.cnf
RUN sed -i 's/MinProtocol = TLSv1.2/MinProtocol = TLSv1/g' /usr/lib/ssl/openssl.cnf
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /usr/lib/ssl/openssl.cnf

WORKDIR /app/SampleAPI
COPY --from=build-env /app/SampleAPI .
WORKDIR /app/SampleAPI/bin/Production/netcoreapp3.1

ENTRYPOINT ["dotnet", "SampleAPI.dll"]



Build Docker image

docker build -t sampleapi:latest .


Run Docker container 

docker run -rm -p 5000:80 sampleapi:latest

where 80 is default port of docker container and 5000 port to expose to internet. 

Browse the API and it should respond with successful database connection. 

Alternatively

bionic version of aspnet core image can be used - 
FROM mcr.microsoft.com/dotnet/core/sdk:3.1-bionic AS build-env
WORKDIR /app

# Copy csproj and restore as distinct layers
COPY /DPRR-API/*.csproj ./
RUN dotnet restore

# Copy everything else and build
COPY . .
WORKDIR /app/DPRR-API
RUN dotnet publish -c Production -o publish

# Build runtime image
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-bionic

WORKDIR /app/DPRR-API
COPY --from=build-env /app/DPRR-API .
WORKDIR /app/DPRR-API/bin/Production/netcoreapp3.1

ENTRYPOINT ["dotnet", "DPRR-API.dll"]

By using bionic image of aspnet core(mcr.microsoft.com/dotnet/core/sdk:3.1-bionic), there should not be any need of modifying the TLS or default settings.

Please share your feedback if it works for you. 

Comments

  1. It is perfect chance to make a couple of game plans for the future and the opportunity has arrived to be sprightly. I've scrutinized this post and if I may I have the option to need to suggest you some interesting things or recommendations. Perhaps you could create next articles insinuating this article. I have to examine more things about it!pmp certification in malaysia

    ReplyDelete
    Replies
    1. Thanks for sparing out time to write comment on post. Please elaoborate more on what you would like to advice.

      Delete
  2. cool stuff you have and you keep redesign all of us
    HRDF training

    ReplyDelete
  3. This is such a great resource that you are providing and you give it away for free.
    digital marketing courses in hyderabad with placements

    ReplyDelete

  4. If you don"t mind proceed with this extraordinary work and I anticipate a greater amount of your magnificent blog entries
    Digital Marketing Training Institutes in Hyderabad

    ReplyDelete
  5. All things considered I read it yesterday however I had a few considerations about it and today I needed to peruse it again on the grounds that it is very elegantly composed.
    data scientist course

    ReplyDelete
  6. I commend you for your excellent report on the knowledge that you have shared in this blog.
    360DigiTMG data analytics course

    ReplyDelete
  7. Extremely overall quite fascinating post. I was searching for this sort of data and delighted in perusing this one. Continue posting. A debt of gratitude is in order for sharing. python course in delhi

    ReplyDelete

Post a Comment

Popular posts from this blog

Cannot alter the login 'sa', because it does not exist or you do not have permission.

Working on projects, it can happen that 'sa' account gets locked. If it is on local machine OR development boxes, onus would be on you to fix it. If scripts and SQL steps are not working, this might help you fixing the issue. Steps to unlock 'sa' account and resetting the password. 1. Open SQL Server Configuration Manager 2. Select SQL Server Services -> 'SQL Server' service. 3. Right click on 'SQL Server' service and click on "Startup Parameters". For 2008, server "Startup Parameters" are inside Advanced tab.   4. Add '-m' in startup parameters as shown above and click on 'Add'. This will put SQL server into 'Single User Mode' and local admin will have 'Super User' rights. For 2008, server you have to add ':-m' in the last of the existing query. 5. Save the settings and Restart the service. 6. Now open the SQL Server Management Studio and connect to database using 'Windows A

Could not load file or assembly 'Microsoft.Web.Infrastructure'

Could not load file or assembly 'Microsoft.Web.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. What 'Micorosoft.Web.Infrastructure' does? This dll lets HTTP modules register at run time. Solution to above problem: Copy 'Micorosoft.Web.Infrastructure' dll in bin folder of your project and this problem should be resolved. If you have .Net framework installed on machine, this dll should be present on it. You can search for this dll and copy it in your active project folder.   Alternatively,  you can install this dll using nuget package manager PM> Install-Package Microsoft.Web.Infrastructure -Version 1.0.0 Happy coding!!