Docker Compose development profile change in JHipster 8 Spring Boot 3 migration

Establishing a repeatable local development environment for JHipster-generated applications requires a stable Docker Compose baseline across teams.

The documented configuration transition with the Spring Boot 3 and Java 17 baseline in JHipster 8+ changed service profiles, healthcheck expectations and environment variable conventions compared with JHipster 7 Spring Boot 2 projects. The shift also overlaps with the documented move away from Netflix Eureka toward Spring Cloud Gateway and Config Server patterns, leaving the canonical local microservice bootstrap undefined in generated projects.

Version sensitivity and host Docker Compose differences add uncertainty about which profiles and files define the repeatable dev baseline.

What profiles and environment variables are documented as the default for repeatable local Docker Compose runs in JHipster 8+ monolith and microservice archetypes? Which configuration files define the compatibility boundary between JHipster 7 Spring Boot 2 and JHipster 8+ Spring Boot 3 development profiles? Is there a documented canonical local bootstrap for microservices after the Eureka deprecation?