Unable to restore packages from private Nuget feed with .Net 8 SDK images.

[darickc]

I have a dockerfile which uses a private Nuget feed to restore packages using the .Net 7 sdk image. I am able to run this using Docker Desktop and through our local Azure Devops pipeline without issues. By only changing to the .Net 8 sdk image, it now fails when doing the restore with the following error "error NU1301: Unable to load the service index for source https://tfs.example.com/tfs/Default/_packaging/nuget/v3/index.json." I've tried several other ways based on this link https://github.com/dotnet/dotnet-docker/blob/main/documentation/scenarios/nuget-credentials.md including using Azure Artifact Credential Provider without success. What has changed in the .Net 8 images that this no longer works? The PAT is passed in through an environment variable.

old dockerfile
`
FROM mcr.microsoft.com/dotnet/sdk:7.0 AS build
WORKDIR /app

ARG PAT

COPY . ./
WORKDIR /app/myApp.Api
RUN dotnet nuget update source myFeed --valid-authentication-types basic --username "docker" --password "${PAT}" --store-password-in-clear-text
RUN dotnet restore
RUN dotnet publish -c Release -o out

FROM mcr.microsoft.com/dotnet/aspnet:7.0 AS runtime
WORKDIR /app
COPY --from=build /app/myApp.Api/out ./
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf
RUN apt-get update && apt-get -y install gss-ntlmssp
ENTRYPOINT ["dotnet", "myApp.Api.dll"]
`

new dockerfile
`
FROM mcr.microsoft.com/dotnet/sdk:8.0 AS build
WORKDIR /app

ARG PAT

COPY . ./
WORKDIR /app/myApp.Api
RUN dotnet nuget update source myFeed --valid-authentication-types basic --username "docker" --password "${PAT}" --store-password-in-clear-text
RUN dotnet restore
RUN dotnet publish -c Release -o out

FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS runtime
WORKDIR /app
COPY --from=build /app/myApp.Api/out ./
RUN sed -i 's/DEFAULT@SECLEVEL=2/DEFAULT@SECLEVEL=1/g' /etc/ssl/openssl.cnf
RUN apt-get update && apt-get -y install gss-ntlmssp
ENTRYPOINT ["dotnet", "myApp.Api.dll"]
`

NuGet.config
<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="myFeed" value="https://tfs.example.com/tfs/Default/_packaging/nuget/v3/index.json" /> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> </packageSources> </configuration>

[lbussell]

One thing you could try to help pinpoint the issue is to print the content of your NuGet.config file after running dotnet nuget update source to make sure that your PAT made it into the file correctly - something like RUN echo NuGet.config.

[alessandro-gandolfi-ors]

I'm currently having the same problem when trying to build images that need a private repository, running "dotnet publish".

I tried to:

• use a file NuGet.Config in the same directory as the solution
• use a file nuget.config in the same directory as the solution
• run "dotnet source add" that (by reading the log) was successful
  • Package source with Name: XXXXX added successfully.

All these attempts were made without using any replacement or valorization of the credentials. Running "dotnet restore" before "dotnet publish" doesn't change anything other than encountering in the previous (restore) command.

The NuGet.Config file was working when using Visual Studio 2022 and it was correctly recognized to install the packages.

These errors began to appear when trying to run the build in Jenkins, using the 8.0 SDK image to build the projects. When searching for the packages to be restores, nuget only searches in the public repositories (nuget.org, https://nuget.ors.it/NuGet/nuget) but never in the private ones.

[lbussell]

@alessandro-gandolfi-ors, can you share your Dockerfile, or at least the build portion of it? If NuGet is searching only nuget.org, it sounds like your NuGet config isn't making it into the container at build time.

[alessandro-gandolfi-ors]

@lbussell nevermind, in the project that needed the private repository there was a property in the csproj to define the sources of the nuget packages. i changed it to be more adequate to my case of use and now it seems to work fine. thanks for the support!