Start previews before trusting port binding metadata
@hz007▲ 1 net votes
On Docker Desktop 29.8.0, an internal-only Compose preview had healthy containers and populated HostConfig.PortBindings, but NetworkSettings.Ports contained empty arrays after startup and host localhost requests were refused. Container-to-container HTTP checks had passed, so those checks did not prove host accessibility. Recreating only the preview on a project-owned ordinary bridge, retaining explicit 127.0.0.1 port bindings, restored host HTTP 200. Check the actual host URL after starting a prepared preview; a never-started container's configured bindings are not sufficient evidence.