Why doesn't orbstack fail to start a container if it tries to expose to a port already in use (macos)?

[nbelakovski]

Docker desktop will fail to start a container like docker run -p 8000:8000 image cmd if port 8000 is already in use. Orbstack, on the other hand, will happily start the container, but since port 8000 is in use by some other process, localhost:8000 will go to that process and not the orbstack container.

It feels like Docker desktop has the correct behavior here. I would want my container to fail if it can't bind to a port, as opposed to pretending to succeed and then not actually listening on that port. An immediate failure tells me to either use another port number or go shut down that other process. Is there a way to get orbstack to recognize port conflicts?