SA1781079 - NetCore - Unable to start the Spire and Classic containers

  • Updated

We are seeing an issue with the recent LTS release of Configured Commerce running on NetCore (Net8.0) where the Spire and Classic containers are unable to start in local Docker environment. The error appears as below:

2025-10-21 17:54:05 Generating Nginx config at /etc/nginx/templates/default.conf.template...
2025-10-21 17:54:05 Get-Content: /nginx/generateNginxConfig.ps1:21
2025-10-21 17:54:05 Line |
2025-10-21 17:54:05   21 |  $routes = (Get-Content $routesYamlLocation | ConvertFrom-Yaml)
2025-10-21 17:54:05      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2025-10-21 17:54:05      | Cannot find path '/config/routes.yaml' because it does not exist.

 

Reported Version

5.2.2508.2308+lts

Cause

We made changes to improve our routing configuration but missed that the routes.yaml file was not distributed and configured in the released version of code. A fix will be implemented in the next release/hotfix. For the time being, please try the following workaround provided by our Product Team:

Workaround

Modify docker-compose.yml to add the two volumes properties seen below:

  classic-proxy: 
    image: optimizelyb2bpublic.azurecr.io/commerce/reverse-proxy:${IMAGE_TAG} 
    ports: 
      - ${CLASSIC_PORT}:80 
    environment: 
      FRONTEND: storefront-api 
      CONTENT_ADMIN: admin-api 
    env_file: 
      - ./.env 
    volumes: 
      - ./.config/reverse-proxy/routes.yaml:/config/routes.yaml 

  spire-proxy: 
    image: optimizelyb2bpublic.azurecr.io/commerce/reverse-proxy:${IMAGE_TAG} 
    ports: 
      - ${SPIRE_PORT}:80 
    environment: 
      FRONTEND: spire 
      CONTENT_ADMIN: spire 
    env_file: 
      - ./.env 
    volumes: 
      - ./.config/reverse-proxy/routes.yaml:/config/routes.yaml

Save the attached routes.yaml file to .config/reverse-proxy/routes.yaml .