Docker
Read-only Docker Engine awareness on host port bindings.
When Docker Engine is present, PortPilot attaches container metadata to host bindings: name, image, published ports, health when reported.
This is read-only. PortPilot does not start, stop, exec, or manage Compose/Kubernetes.
How it helps
A published container port on the host shows which container owns it, the image, and whether the engine reports the container running. Use that before you Kill process (you may be aiming at docker-proxy rather than the app).
CLI: portpilot docker, portpilot docker ports, portpilot docker container <id>.
Expected result
Port rows with Docker show a container strip. Engine unavailable → ordinary host ports still list.
Docker troubleshooting
| Symptom | Recovery |
|---|---|
| Docker not detected | Engine not installed, or agent cannot see the pipe/socket |
| Permission issue | Linux: portpilot user is not in the docker group (do not add it unless you accept engine access) |
| Daemon unavailable | Start Docker Engine; re-scan |
| Container unavailable / stopped | Start it with Docker yourself — PortPilot will not |
| Unexpected mapping | Check docker ps published ports; PortPilot mirrors Engine |