Error about port conflict (when docker container is already running in background)

Occasionally (not sure when, maybe when computer goes to sleep, or when shell is closed by vscode, or something), the dotrun process ends, but the docker container in the background still runs.

This causes a conflict of port number when I try to run dotrun again

I have to manually stop given container in docker to be able to use dotrun again.

Dotrun containers have a unique names now, but listening on the same port still is blocking running another container if one is already running.

Would it be possible for dotrun to detect container running on given port and close it or something?

Reproduce the failure by leaving a dotrun Docker container running, then starting dotrun again with the same port. Trace dotrun's container startup and cleanup entry points to determine how the conflicting container is identified. Done means a repeated start no longer requires manually stopping the old container, with the existing behavior preserved when no conflict exists.

Written by the indexing model from the issue text.