ASPNETCORE_URLS from docker-compose did not override appsetting.production.json

Question

I configured my Asp.Net core project with compose-up.

And the secton for web is below:

    server:
        container_name: 'server'
        image: 'mcr.microsoft.com/dotnet/aspnet:5.0'
    #    restart: always
        working_dir: '/app'
        ports: 
            - "8886:80"
            - "8887:443"
        volumes: 
            - 'C:/Users/xx/Docker/meekou-server/:/app'
            - 'C:\Users\xx\Docker\meekou-certificates\https:/https/'
        environment: 
            - ASPNETCORE_ENVIRONMENT=Production
            - ASPNETCORE_URLS=http://+:80
            - ASPNETCORE_Kestrel__Certificates__Default__Password=test
            - ASPNETCORE_Kestrel__Certificates__Default__Path=/https/aspnetapp.pfx
        entrypoint: 
            ["dotnet", "xx.Web.Host.dll"]           
        depends_on: 
            - meekou-mysql

And there is config from appsettings.Production.json

  "Kestrel": {
    "Endpoints": {
      "Http": {
        "Url": "http://+:809"
      }
    }
  },

With compose-up, the asp.net core always listen under 809.

Is there any reason, the docker-compose file did not override the settings from appsettings.Production.json?

Kirk Larkin · Accepted Answer · 2021-12-14 14:14:37Z

2

The configuration in appsettings.Production.json takes precedence over the ASPNETCORE_URLS environment variable. More specifically, configuration in a Kestrel section overrides the Urls configuration setting.

If you override the configuration key that represents the Kestrel endpoint you've configured in appsettings.Production.json, using the ASPNETCORE_KESTREL__ENDPOINTS__HTTP__URL environment variable, it works:

environment: 
    - ASPNETCORE_ENVIRONMENT=Production
    - ASPNETCORE_KESTREL__ENDPOINTS__HTTP__URL=http://+:80

edited Dec 14, 2021 at 14:14

answered Dec 14, 2021 at 14:09

Kirk Larkin

94.4k17 gold badges235 silver badges214 bronze badges

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

4 Comments

Hans Kilian Over a year ago

Normally environment variables take precedence over config file settings. Do you know why that isn't the case here?

Kirk Larkin Over a year ago

@HansKilian It's less about configuration sources overriding others, and more about Kestrel preferring "endpoints" keys over the higher-level "urls" key. There's a test in the source that demonstrates this here. You can follow that through the AddressBinder.BindAsync method to see more about how it works.

Edward Over a year ago

@KirkLarkin I made a test with ASPNETCORE_KESTREL__ENDPOINTS__HTTP__URL under .net 5, it seems it does not work. I am afraid I need to modify the appsettings.Production.json

Vitalii Ivanov Over a year ago

@Edward try Kestrel__EndPoints__Http__Url=http://+:80, works for me

Collectives™ on Stack Overflow

ASPNETCORE_URLS from docker-compose did not override appsetting.production.json

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related