Hi @jon1123 - I have no experience or knowledge about Caddy, so I am only guessing, but here’s my first couple thoughts:
- I would recommend using the 8.7 release. 8.8 is in alpha stages and there are known issues with the current Docker release (example). The 8.7 release is stable and working.
- The networks in the caddy image is missing
identity-network - Camunda’s Docker config doesn’t use profiles, perhaps try testing without them to ensure everything is always starting together? Though I doubt this is related to the error
- If you take Caddy out of the configuration and just start the Camunda services, do they start? If not, what doesn’t start and what do the logs show?
- If this config without Caddy doesn’t start, what if you try from scratch with the 8.7 docker-compose.yaml config? If that doesn’t start, what containers don’t start and what do the logs show?