If a managed database container is deployed with a config file mounted into the container and that config file specifies a non-default port, then defang will not know about it. Defang will assume the default port for these services when wiring up networking.
We currently consider this to be a corner case which is not worth the complexity to solve, but we should mention it in the docs, so that the AI debugger (or an intrepid reader) may find it.