Docker / Networking, Ports & Service Connectivity
Investigate published Swarm service ports through the routing design
A Swarm service can publish via ingress routing mesh or host mode, which affects which nodes accept traffic.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker service inspect --format '{{json .Endpoint.Ports}}' webRead the result
Run with approved Swarm manager access. Published port definitions show intent but do not prove healthy tasks or node firewall paths.
Resolve and verify
Compare publish mode, task placement and node reachability with the supported design. Repair the specific service or network dependency and test the real client path.
Before changing production
Do not assume ordinary docker run port behavior applies unchanged to a Swarm service.