What cause Drive Sharing Errors?

General
1

Hello there,

My name is Vincent, and I’ve been working in a multi-application contianer environment for over a year now.
There are half a dozen APIs running a mix of 3.1.2 and 6.0.2 versions of Entity Framework as we are mid-migration.

I had to get my computer re-imaged due to running into some issues merging my API project alongside the existing orchestration. I figured this would surely resolve any issues I had, but I must have something configured incorrectly because I can build all projects except the one I’m trying to merge.

I’ve already verified the paths, my environment file and its contents, as well as that my docker-compose isn’t being overridden incorrectly by Visual Studio.

My understanding regarding the file sharing issue has to do with a WSL2 integration issue message:
am I at least correct in thinking that my problem is thus with my WSL installation on my newly imaged Windows 11 machine?

2

Ah, I apologize! One thing I did forget to mention is that when i go to Docker Desktop > Builders, there is an entry for docker-windows that lists an error out, whereas the docker-linux and default builders seem installed properly:

request returned 500 Internal Server Error for API route and version http://%2F%2F.%2Fpipe%2FdockerDesktopWindowsEngine/_ping, check if the server supports the requested API version

3

Yeah, sounds like a WSL2 integration issue—especially after a re-image. I’d check Docker Desktop’s WSL settings and make sure drive/file sharing is properly configured.

4

Your first post is written, in a way that require us to have very specific context knowledge. Fine, if you want to wait for someone that actually can make sense of it.

Usually understanding docker mechanics is enough to help in most cases, though in your case there is not enough information shared, that allows someone not knowing your situation to understand it.

From what you wrote, I can only assume you want to build a Windows container image. I never created one, but I can assume that you need to “switch to windows containers…” mode, to be able to create windows container images, and start a windows container.

You find the option in the context menu of the Docker Desktop taskbar icon:

image
image948×1434 150 KB

5

Thanks for the replies, I appreciate the push to clarify. As you pointed out, this is my first post!
I can see how my original post assumed too much background context now that it’s been pointed out.

To clarify upfront: I’m working exclusively with Linux containers via WSL2 integration, not Windows containers. Docker Desktop is set to use WSL2 as its backend, and all images involved are based on mcr.microsoft.com/dotnet/aspnet:6.0 or 3.1.

Update on path / network troubleshooting:

  1. Solution file syntax

    • Discovered Portal.sln had 17 Project( but only 16 EndProject lines.
    • Added the missing EndProject for StarRezident.API.UnitTests → restored cleanly locally (dotnet restore) and inside Docker.

  2. Docker / WSL2 file sharing

    • Verified src/Portal.sln and all *.csproj are present in the build context.
    • Individual dotnet restore <proj>.csproj succeeds in both container and host.

  3. Network / TLS connectivity

    • Inside mcr.microsoft.com/dotnet/core/sdk:3.1-bionic, ran:
      curl -v https://api.nuget.org/v3/index.json
      → Received HTTP 200 with valid TLS handshake.
    • Confirms no proxy or CA issues in the container (VPN required).

  4. Current status

    • With the .sln fixed and networking healthy, docker compose build my-admin-api --no-cache now completes the restore step successfully.

Question:
Given that paths, solution syntax, and network/TLS have all been ruled out, any idea what might still block the remaining service builds? Or suggestions on improving this multi-project Docker setup?

Thanks again for your patience and guidance!

6

Even with your extended explanation, I still have no idea what the actual problem is, and whether knowing docker mechanics is enough to help, or whether you need someone who actually works with aspnet.

You didn’t share any Dockerfile or compose file content, or actual error message from during the build or logs.

I am not sure how to provide any guidance here.

7

Ack, my apologies. Got a little buried in the weeds there…
So what’s happening now is I’m trying to run docker-compose up, and now it’s a network issue that seems to be clogging the build process. I’m on my workplace’s VPN and have tried wired + wireless connections.

Hopefully including the below sheds more light on the situation?

Errors from Building

Running the Orchestra

docker-compose up:

Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.abstractions/index.json'.
45.02   The SSL connection could not be established, see inner exception.
45.02     Authentication failed because the remote party has closed the transport stream.
45.02   Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/fluentvalidation/index.json'.
45.02   The SSL connection could not be established, see inner exception.
45.02     Authentication failed because the remote party has closed the transport stream.
45.02   Retrying 'FindPackagesByIdAsync' for source 'https://api.nuget.org/v3-flatcontainer/microsoft.entityframeworkcore.design/index.json'.
45.02   The SSL connection could not be established, see inner exception.
45.02     Authentication failed because the remote party has closed the transport stream.
...
failed to solve: process "/bin/sh -c dotnet restore Portal.sln" did not complete successfully: exit code: 1

docker-compose.yaml

version: '3.4'

services:
  advisor-worksheet-api:
    container_name: 'myuwo_api_worksheets'
    restart: always
    build:
      context: ./src
      dockerfile: Services/AdvisorWorksheet/AdvisorWorksheet.API/Dockerfile
    networks:
      - myuwo_network
    ports:
      - 4201:80
    env_file: C:\ENVrepofiles\AdvisorWorksheet\AdvisorWorksheet.API/.env

  lost-and-found-api:
    container_name: 'myuwo_api_lost_and_found'
    restart: always
    build:
      context: ./src
      dockerfile: Services/LostAndFound/LostAndFound.API/Dockerfile
    networks:
      - myuwo_network
    ports:
      - 4202:80
    env_file: C:\ENVrepofiles\LostAndFound\LostAndFound.API/.env

  my-admin-api:
    container_name: 'myuwo_api_my_admin'
    restart: always
    build:
      context: ./src
      dockerfile: Services/MyAdmin/MyAdmin.API/Dockerfile
    networks:
      - myuwo_network
    ports:
      - 4203:80
    env_file: C:\ENVrepofiles\MyAdmin\MyAdmin.API/.env

  titan-card-api:
    container_name: 'myuwo_api_titan_card'
    restart: always
    build:
      context: ./src
      dockerfile: Services/TitanCard/TitanCard.API/Dockerfile
    networks:
      - myuwo_network
    ports:
      - 4204:80
    env_file: C:\ENVrepofiles\TitanCard\TitanCard.API/.env
  
  logging-api:
    container_name: 'myuwo_api_logging'
    restart: always
    build:
        context: ./src
        dockerfile: Services/LoggingEmailSystem/LoggingEmailSystem.API/Dockerfile
    networks:
    - myuwo_network
    ports:
    - 4208:80 # ITH: 9/24/2024 Changed this to be 4208
    env_file: C:/ENVrepofiles/LoggingEmailSystem/LoggingEmailSystem.API/.env
  
  starrezident-api:
    container_name: 'myuwo_api_starrezident'
    restart: always
    deploy: 
      resources:
        limits:
         memory: 5G
        reservations:
          memory: 3G
    build:
      context: ./src
      dockerfile: Services/StarRezident/StarRezident.API/Dockerfile
    networks:
    - myuwo_network
    ports: 
    - 4210:80
    env_file: C:\ENVrepofiles\StarRezident\StarRezident.API\.env

  security-station-api:
    container_name: 'myuwo_api_security'
    restart: always
    build:
        context: ./src
        dockerfile: Services/SecurityStation/SecurityStation.API/Dockerfile
    networks:
      - myuwo_network
    ports:
    - 4206:80
    env_file: C:/ENVrepofiles/SecurityStation/SecurityStation.API/.env
    
  checkout-api:
    container_name: 'myuwo_api_checkout'
    restart: always
    build:
      context: ./src
      dockerfile: Services/Checkout/Checkout.API/Dockerfile
    networks:
    - myuwo_network
    ports:
    - 4207:80
    env_file: C:\ENVrepofiles\Checkout\Checkout.API\.env
   
  bike-registration-api:
    container_name: 'myuwo_api_bike_registration'
    restart: always
    build:
       context: ./src
       dockerfile: Services/BikeRegistration/BikeRegistration.API/Dockerfile    
    networks: 
       - myuwo_network
    ports:
      - 4205:80
    env_file: C:\ENVrepofiles\BikeRegistration\BikeRegistration.API/.env
  
  door-access-api:
    container_name: 'myuwo_api_door_access'
    restart: always
    build:
      context: ./src
      dockerfile: Services/DoorAccess.API/Dockerfile

    networks: 
      - myuwo_network
    ports:
      - 4209:80
    env_file: C:\ENVrepofiles\DoorAccess\DoorAccess.API/.env
  
  

networks:
  myuwo_network:
    driver: bridge