-
Hello - we are running into an openssl issue with our sql server connection when trying to use the aspnet:8.0-jammy-chiseled-extra image. We have a dependency on an old version of SqlServer so we must modify the openssl.cnf to downgrade the security level. I have produce a Dockerfile which does this successfully when using aspnet:8.0-jammy as the base image, but the openssl.cnf change does not apply when using aspnet:8.0-jammy-chiseled-extra as the base image. I've built this docker file based on suggestions from a similar issue with an earlier chiseled image, but I've updated the openssl fix for net8 based on other threads. Any suggestions or ideas as to what might fix the issue in the chiseled version? Here is the docker file I have been using, and the only change I am making between a working and non-working version is using the aspnet:8.0-jammy-chiseled-extra (not working) -vs- aspnet:8.0-jammy (working) in the final stage.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi, The following configuration worked in my case. FROM mcr.microsoft.com/dotnet/sdk:8.0-jammy AS build
RUN sed -i 's/DEFAULT:@SECLEVEL=2/ALL:@SECLEVEL=0/g' /etc/ssl/openssl.cnf
RUN sed -i 's/DEFAULT:@SECLEVEL=2/ALL:@SECLEVEL=0/g' /usr/lib/ssl/openssl.cnf
...
WORKDIR /src
...
FROM base AS final
COPY --from=build /etc/ssl/openssl.cnf /etc/ssl/openssl.cnf
COPY --from=build /usr/lib/ssl/openssl.cnf /usr/lib/ssl/openssl.cnf
WORKDIR /app
COPY --from=build /app/publish .
... |
Beta Was this translation helpful? Give feedback.
Hi,
The following configuration worked in my case.