unable to upgrade to tcp
instead of port not allocated
#22285
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Issue Description
if port i use already is allocated (i.e. run
podman run -p 4000:4000 -v $(pwd):/site bretfisher/jekyll-serve
twice) I get:I get an error like:
unable to upgrade to tcp, received 409
it would be nice if it would be a bit more informative, like:
port 4000 already allocated
or something similar that can give a hint to user what is the actual cause/fix.Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
see above.
Describe the results you expected
info about port already allocated.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
No response
The text was updated successfully, but these errors were encountered: