Docker for Windows中部署ASP.NET 4.5应用后如何访问该应用？

Hey there! Let's walk through the common issues that might be causing your ASP.NET 4.5 app to not show up (only the default IIS page appears) in your Docker container.

1. Verify Your Dockerfile Copies App Files to the Correct IIS Directory #

By default, IIS's default website uses C:\inetpub\wwwroot as its physical path. If your Dockerfile isn't copying your app files to this location, IIS will just serve the default page.

Check your Dockerfile for a COPY command that moves your application code into the container. It should look something like this:

# Use the appropriate ASP.NET 4.5-compatible base image
FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019

# Copy your app files to the IIS default website directory
COPY . C:\inetpub\wwwroot

If you're copying to a different folder, you'll need to update the IIS site's physical path (see step 2).

2. Check IIS Site Configuration in the Container #

It's possible the IIS site is still pointing to the default wwwroot instead of your app's directory, or your app wasn't set as the default site.

• Enter your container using PowerShell:

  docker exec -it <your_container_id> powershell
  

• List all IIS websites to check their physical paths:

  Get-Website
  

• If your app is in a different directory (e.g., C:\my-app), update the default site's physical path:

  Set-ItemProperty 'IIS:\Sites\Default Web Site' -name physicalPath -value 'C:\my-app'
  

• Restart the IIS service to apply changes:

  net stop was /y
  net start w3svc
  

3. Inspect IIS Logs for Application Errors #

If your app is copied correctly but still not loading, there might be runtime errors preventing it from initializing. Check the IIS logs for clues:

• In the container's PowerShell session, navigate to the log directory:

  cd C:\inetpub\logs\LogFiles\W3SVC1
  

• View the latest log file to look for HTTP error codes (like 500 Internal Server Error):

  type *.log
  

Common issues here include missing dependencies, invalid web.config settings, or permission problems with your app files.

4. Confirm Port Access (If You Switch to Host Port Mapping) #

While you're accessing the container IP directly right now, if you later want to use your host machine's IP, make sure you've mapped port 80 (or your app's port) in your docker run command:

docker run -d -p 8080:80 <your_image_name>

Then you can access the app via http://localhost:8080.

5. Ensure Your App is Compatible with the Base Image #

Double-check that you're using a base image that supports ASP.NET 4.5. The official mcr.microsoft.com/dotnet/framework/aspnet images (like 4.8) work for ASP.NET 4.5 apps since they're backward compatible. Avoid using a plain Windows Server Core image without the ASP.NET framework pre-installed.

内容的提问来源于stack exchange，提问作者DiPix