C# 在Docker容器中运行时,Swigger未打开
在我的项目中,我在Startup.cs中设置了Swashback和Swashback:C# 在Docker容器中运行时,Swigger未打开,c#,.net,docker,swagger,C#,.net,Docker,Swagger,在我的项目中,我在Startup.cs中设置了Swashback和Swashback: public void Configure(IApplicationBuilder app, IHostingEnvironment env) { app.UseSwagger(); app.UseSwaggerUI(c => { c.SwaggerEndpoint("/swagger
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseSwagger();
app.UseSwaggerUI(c =>
{
c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
});
当我从VisualStudio运行我的应用程序时,我可以访问localhost:123456/swagger
并获得API文档,就像它应该的那样。然而,当我使用Docker compose up和access通过Docker运行我的应用程序时,它只是将我的应用程序重新路由到我的应用程序首页,没有任何招摇过市的页面或错误,只是返回到同一页面,就好像我根本没有写/swagger
。我尝试了几种不同的URL,/swagger
,/swagger ui.html
等,但没有区别。在Docker容器中运行时,是否有任何特定配置必须写入Docker文件或其他地方才能访问Swagger文档
Docker编写文件:
version: "3.7"
services:
node-frontend:
container_name: node-frontend
build: ./ClientApp/
command: npm run start
ports:
- "3000:3000"
dotnet-backend:
container_name: dotnet-backend
build: .
#expose:
# - "80"
links:
- mssql-db
ports:
- "8000:80"
nginx-reverse-proxy:
container_name: nginx-reverse-proxy
build: ./nginx/
#command: tail -F /dev/null
command: nginx -g 'daemon off;'
ports:
- "80:80"
# - "443:443"
expose:
- "80"
- "443"
links:
- node-frontend
- dotnet-backend
mssql-db:
container_name: mssql-db
#image: mcr.microsoft.com/mssql/server:2019-latest
build: ./Database
environment:
- SA_PASSWORD=password
- ACCEPT_EULA=Y
volumes:
- ./Database/:/scripts/
ports:
- "1433:1433"
expose:
- "1433"
command:
- /bin/bash
- -c
- |
Dockerfile:
FROM mcr.microsoft.com/dotnet/core/sdk:2.2 AS build-env
WORKDIR /app
# Copy csproj and restore as distinct layers
COPY *.csproj ./
RUN dotnet restore
# Copy everything else and build
COPY . ./
RUN dotnet publish -c Debug -o out Project.csproj
# Build runtime image
FROM mcr.microsoft.com/dotnet/core/aspnet:2.2
WORKDIR /app
COPY --from=build-env /app/out .
EXPOSE 80
ENTRYPOINT ["dotnet", "ProjectApi.dll", "--environment=Development"]
共享你的docker compose文件。在原始问题中添加了docker compose文件。你是否找到了这个问题的底部?你是否找到了工作?我也被困在同一点上…共享你的docker compose文件。在原始问题中添加了docker compose文件。你了解这个问题的底部了吗?你知道了吗?我被困在同一点上。。。。