Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker-compose up failing because "port is already allocated" #4950 - reopen? #9117

Closed
MikeB2019x opened this issue Jan 21, 2022 · 3 comments
Labels

Comments

@MikeB2019x
Copy link

Using version: docker-compose version 1.29.2, build 5becea4

I'm not sure why this issue is closed. There are reports right up until today. If you have to stop and then restart docker (as many have) then that's not a fix, it's a bug. If you have to take extra steps to clean the environment after stopping a container, then that's a bug ie.

docker-compose down
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
launchctl list | grep docker
launchctl stop com.docker.docker.<number>

I'd suggest this be kept/re-opened until it's resolved.

@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 31, 2022
@stale
Copy link

stale bot commented Nov 2, 2022

This issue has been automatically closed because it had not recent activity during the stale period.

@jinek
Copy link

jinek commented Jul 10, 2023

#4950 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants