Reproduction
- Deploy a project on a fixed host port.
- Leave a cancelled or stale OpenShip container bound to that port, with
openship.project and openship.deployment labels.
- Redeploy the project while
activeDeploymentId references a deployment whose recorded container is missing.
- Open the port-conflict prompt.
Actual behavior
OpenShip attributes the docker-proxy listener to docker.service and offers Stop Service & Continue. Choosing it would stop the Docker daemon and every hosted app instead of the container that owns the port.
Expected behavior
Resolve docker-proxy to the container publishing the port and use its OpenShip labels to identify ownership. Offer to stop only that container. Never offer to stop docker.service for an application port conflict. If ownership is ambiguous, fail safely and require manual resolution.
Reproduction
openship.projectandopenship.deploymentlabels.activeDeploymentIdreferences a deployment whose recorded container is missing.Actual behavior
OpenShip attributes the
docker-proxylistener todocker.serviceand offers Stop Service & Continue. Choosing it would stop the Docker daemon and every hosted app instead of the container that owns the port.Expected behavior
Resolve
docker-proxyto the container publishing the port and use its OpenShip labels to identify ownership. Offer to stop only that container. Never offer to stopdocker.servicefor an application port conflict. If ownership is ambiguous, fail safely and require manual resolution.