Local Docker deployment for single tiered application with sql server #5260

7 Answer(s)

• 

  0

  rafael.gonzales created one year ago

  Can you share your dockerfile and docker-compose?

  Save Cancel
• 

  0

  gterdem created one year ago

  Senior .NET Developer

  Please check https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-docker-compose?UI=MVC&DB=EF&Tiered=No

  Save Cancel
• 

  0

  Sraman created one year ago

  Please check https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-docker-compose?UI=MVC&DB=EF&Tiered=No

  Can you suggest some production deployment ideas using above code?

  Save Cancel
• 

  0

  Sraman created one year ago

  Can you share your dockerfile and docker-compose?

  I'm able to do build and run container on my docker desktop with the below docker files using build-images-locally.ps1and run-docker.ps1.

  But how should I use my docker file to deploy on production to docker container registry. What changes should I make or any suggestions?

    FROM mcr.microsoft.com/dotnet/aspnet:7.0
    COPY bin/Release/net7.0/publish/ app/
    WORKDIR /app
    ENTRYPOINT ["dotnet", "Acme.Books.dll"]
  

  version: '3.9'
  
  services:
    mrs-web:
      image: pentapack/mrs:latest
      container_name: mrs-web
      build:
        context: ../../
        dockerfile: Pentapack.MRS/Dockerfile.local
      environment:
        - ASPNETCORE_URLS=https://+:443;http://+:80;
        - Kestrel__Certificates__Default__Path=/root/certificate/localhost.pfx
        - Kestrel__Certificates__Default__Password=91f91912-5ab0-49df-8166-23377efaf3cc
        - ConnectionStrings__Default=Server=mrs-db,1433;Database=MRS;User=sa;Password=Aqwx1379!;TrustServerCertificate=true;
      ports:
        - "443:443"
      depends_on:
        mrs-db:
          condition: service_healthy
      restart: on-failure  
      volumes:
        - ./certs:/root/certificate
      networks:
        - mrs-network
  
    mrs-db-migrator:
      image: pentapack/mrs:latest
      container_name: mrs-db-migrator
      build:
        context: ../../
        dockerfile: Pentapack.MRS/Dockerfile.local
      environment:
        - ConnectionStrings__Default=Server=mrs-db,1433;Database=MRS;User=sa;Password=Aqwx1379!;TrustServerCertificate=true;
      command:
        - --migrate-database
      depends_on:
        mrs-db:
          condition: service_healthy
      networks:
        - mrs-network 
  
    mrs-db:
      container_name: mrs-db
      image: 'mcr.microsoft.com/mssql/server:latest'
      ports:
        - "1433:1433"
      volumes:
        - mrs-data:/data/db
      environment:
        - ACCEPT_EULA=Y
        - SA_PASSWORD=Aqwx1379!
      networks:
        - mrs-network
      healthcheck:
        test: ["CMD", "/opt/mssql-tools/bin/sqlcmd", "-Usa", "-PAqwx1379!", "-Q", "select 1"]
        interval: 10s
        timeout: 10s
        retries: 10
  volumes:
    mrs-data:
      name: mrs-data
  networks:
    mrs-network:
      name: mrs-network
      driver: bridge
  

  Save Cancel
• 

  0

  gterdem created one year ago

  Senior .NET Developer

  Please read https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-docker-compose?UI=MVC&DB=EF&Tiered=No

  There is a detailed explanation about what to override, how to override and why to override.

  Save Cancel
• 

  0

  Sraman created one year ago

  Please read https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-docker-compose?UI=MVC&DB=EF&Tiered=No

  There is a detailed explanation about what to override, how to override and why to override.

  I'm confused with Db Migrator, no tiered application don't have DbMigrator.dll. How can we migrate database without that?

  Save Cancel
• 

  0

  gterdem created one year ago

  Senior .NET Developer

  Okay sorry, I thought you are using non-tiered app template but you are basically using no-layered app template.

  DbMigration in no-layered application template is done by passing the argument --migrate-database.

  The initial docker-compose file generated with the template (mrs-db-migrator service in your application) basically runs as db-migrator and exits if you examine the Program.cs:

  if (IsMigrateDatabase(args))
  {
      await app.Services.GetRequiredService<MyAppDbMigrationService>().MigrateAsync();
      return 0;
  }
  

  So the docker-compose file runs the same docker image as 2 different services:

  • One of them is the application itself: mrs-web
  • Other one is the db-migrator: mrs-db-migrator

  So, when you run the docker-compose file, it will look like:

  

  Which indicates the Exited (0) one is being the db-migrator. You can perfectly use it as it is just fine.

  Another way

  You can also drop using the db-migrator and simply migrate your database whenever you run your application.

  Simply override the OnPostApplicationInitializationAsync and add:

  public override async Task OnPostApplicationInitializationAsync(ApplicationInitializationContext context)
  {
      await context.ServiceProvider
          .GetRequiredService<MyAppDbMigrationService>()
          .MigrateAsync();
  }
  

  This will run the db-migration after your application is initialized instead of manually triggering it with an argument. You can also drop the mrs-db-migrator service in the docker-compose file if you choose to do so.

  Save Cancel