Why is asp.net core microservice returning 404?

Question

I wrote a small demo to understand microservices and DDD. This is the file structure.

├───.dockerignore
├───docker-compose.yml
├───Dockerfile
├───MicroserviceDemo.sln
├───MicroserviceDemo.Application
│   ├───MicroserviceDemo.Application.csproj
│   └───...
├───MicroserviceDemo.Domain
│   ├───MicroserviceDemo.Domain.csproj
│   └───...
└───MicroserviceDemo.Infrastructure
    ├───MicroserviceDemo.Infrastructure.csproj
    └───...

If I run docker compose, the container run fine but I get a 404 when navigating to localhost:5000/swagger.

I tried creating another dockerfile (using VS docker tools), at the application directory, which resulted in normal behavior when running that container (I get the swagger ui). The application also works fine when debugging without dockers running directly on my local with VS).

I am not really sure where the problem could be.

Dockerfile

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY ["MicroserviceDemo.Application/MicroserviceDemo.Application.csproj", "MicroserviceDemo.Application/"]
COPY ["MicroserviceDemo.Infrastructure/MicroserviceDemo.Infrastructure.csproj", "MicroserviceDemo.Infrastructure/"]
COPY ["MicroserviceDemo.Domain/MicroserviceDemo.Domain.csproj", "MicroserviceDemo.Domain/"]

RUN dotnet restore "MicroserviceDemo.Application/MicroserviceDemo.Application.csproj"
COPY . .

WORKDIR "/src/MicroserviceDemo.Application"
RUN dotnet build "MicroserviceDemo.Application.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "MicroserviceDemo.Application.csproj" -c Release -o /app/publish

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "MicroserviceDemo.Application.dll"]

docker-compose.yml

version: '3'
services:
  infrastructure:
    image: "mcr.microsoft.com/mssql/server"
    container_name: microservice-demo-database
    restart: always
    environment:
      SA_PASSWORD: "Your_password123"
      ACCEPT_EULA: "Y"
    ports:
      - 5432:5432
  rabbitmq:
    image: rabbitmq:3-management
    container_name: microservice-demo-rabbitmq
    ports:
      - 5672:5672
      - 15672:15672
    environment:
      - RABBITMQ_DEFAULT_USER=user
      - RABBITMQ_DEFAULT_PASS=password
  api:
    image: microservice-demo:latest
    build: .
    container_name: microservice-demo-api
    restart: always
    depends_on:
      - infrastructure
      - rabbitmq
    ports:
      - 5000:80
      - 5001:443

Hans Kilian · Accepted Answer · 2022-01-18 15:29:43Z

2

By default, Swagger is only available in development mode. Apps in containers are, by default, in production mode.

To run in development mode, you can set the ASPNETCORE_ENVIRONMENT variable to Development and Swagger should become available.

  api:
    image: microservice-demo:latest
    build: .
    container_name: microservice-demo-api
    restart: always
    depends_on:
      - infrastructure
      - rabbitmq
    environment:
      - ASPNETCORE_ENVIRONMENT=Development
    ports:
      - 5000:80
      - 5001:443

answered Jan 18, 2022 at 15:29

Hans Kilian

26.6k4 gold badges39 silver badges56 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

sebsmgzz Over a year ago

I feel so dumb now, I was almost sure it was something regarding ssl certs or https redirection. Thanks for answer!!

Collectives™ on Stack Overflow

Why is asp.net core microservice returning 404?

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related