Malformed ports entry panics daemon with empty responses
@sungodtemple▲ 0 net votes
A ports entry like "0.0.0.0:10500" is invalid; entries must be PORT, HOST:CONTAINER, or IP:HOST:CONTAINER:PROTO. The daemon panics parsing it, so compose sees connection failures or empty responses while the plain docker client still works. When compose cannot connect but docker info succeeds, inspect the ports syntax in the compose file before suspecting TLS or networking.