ubuntu docker ubuntu-14.04 bind docker-compose (2023)

I upgraded my docker this afternoon and ran into the same problem. I tried restarting docker but no luck.

Finally, I had to restart my computer and it worked. Definitely a bug.

On my machine a PID was not being shown from this command netstat -tulpn for the in-use port (8080), so i could not kill it, killing the containers and restarting the computer did not work. So service docker restart command restarted docker for me (ubuntu) and the port was no longer in use and i am a happy chap and off to lunch.

I came across this problem. My simple solution is to remove the mongodb from the system

Commands to remove mongodb in Ubuntu:

sudo apt-get purge mongodb mongodb-clients mongodb-server mongodb-devsudo apt-get purge mongodb-10gen sudo apt-get autoremove

I was getting the below error when i was trying to launch a new container -

listen tcp 0.0.0.0:8080: bind: address already in use.

To check which process is running on port 8080, run below command:

netstat -tulnp | grep 8080

i got the output below

[root@ip-112-x6x-2x-xxx.xxxxx.compute.internal (aws_main) ~]# netstat -tulnp | grep 8080 tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN **12749**/java [root@ip-112-x6x-2x-xxx.xxxxx.compute.internal (aws_main) ~]#

run

kill -9 12749

Then try to relaunch the container it should work

Before it was running on :docker run -d --name oracle -p 1521:1521 -p 5500:5500 qa/oracleI just changed the port to docker run -d --name oracle -p 1522:1522 -p 5500:5500 qa/oracle

it worked fine for me !

I had apache running on my ubuntu machine. I used this command to kill it!

sudo /etc/init.d/apache2 stop

In some cases it is critical to perform a more in-depth debugging to the problem before stopping a container or killing a process.

Consider following the checklist below:

1) Check you current docker compose environment
Run docker-compose ps.
If port is in use by another container, stop it with docker-compose stop <service-name-in-compose-file> or remove it by replacing stop with rm.

2) Check the containers running outside your current workspace
Run docker ps to see list of all containers running under your host.
If you find the port is in use by another container, you can stop it with docker stop <container-id>.
(*) Because you're not under the scope of the origin compose environment - it is a good practice first to use docker inspect to gather more information about the container that you're about to stop.

3) Check if port is used by other processes running on the host
For example if the port is 6379 run:

$ sudo netstat -ltnp | grep ':6379'tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 915/redis-server 12 tcp6 0 0 ::1:6379 :::* LISTEN 915/redis-server 12

(*) You can also use the lsof command which is mainly used to retrieve information about files that are opened by various processes (I suggest running netstat before that).

So, In case of the output above the PID is 915. Now you can run:

$ ps j 915 PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 1 915 915 915 ? -1 Ssl 123 0:11 /usr/bin/redis-server 127.0.0.1:6379

And see the ID of the parent process (PPID) and the execution command.
You can also run: $ pstree -s <PID> to a visual display of the process and its related processes.

In our case we can see that the process probably is a daemon (PPID is 1) - In that case consider running:
A) $ cat /proc/<PID>/status in order to get a more in-depth information about the process like the number of threads spawned by the process, its capabilities, etc'.
B) $ systemctl status <PID> in order to see the systemd unit that caused the creation of a specific process. If the service is not critical - you can stop and disable the service.

4) Restart Docker service
Run: sudo service docker restart.

5) You reached this point and..
Only if its not placing your system at risk - consider restarting the server.

I had same problem,docker-compose down --rmi all (in the same directory where you run docker-compose up)helps

UPD: CAUTION - this will also delete the local docker images you've pulled (from comment)

A variation of @DmitrySandalov's answer: I had tomcat/java running on 8080, which needed to keep going. Looked at the docker-compose.yml file and altered the entry for 8080 to another of my choosing.

nginx: build: nginx ports: #- '8080:80' <-- original entry - '8880:80' - '8443:443'

Worked perfectly. (The only wrinkle is the change will be wiped if I ever update the project, since it's coming from an external repo.)

In my case, using Linux Ubuntu 22, the problem was that exists another container running under root user.

So I did it bellow:

// Stop all running containers of standard userdocker stop $(docker ps -aq)// Change to root usersudo -i// Stop all running containers of root userdocker stop $(docker ps -aq)// Back to your standard userexit

After that I released Redis port 6379, and I could run again my project and everything went well.

For Linux/Unix:

Simple search for linux utility using following command

netstat -nlp | grep 8888

It'll show processing running at this port, then kill that process using PID (look for a PID in row) of that process.

kill PID

You can kill the process listening on that port easily with one command below :

kill -9 $(lsof -t -i tcp:<port#>)

ex :

kill -9 $(lsof -t -i tcp:<port#>)

or for ubuntu:

sudo kill -9 `sudo lsof -t -i:8000`

Man page for lsof : https://man7.org/linux/man-pages/man8/lsof.8.html

-9 is for hard kill without checking any deps.

(Not related, but might be useful if its PORT 5000 mystery) - the culprit process is due to Mac OS monterery.

The port 5000 is commonly used to serve local development servers. When updating to the latest macOS operating system, I was unable the docker to bind to port 5000, because it was already in use. (You may find a message along the lines of Port 5000 already in use.)

By running lsof -i :5000, I found out the process using the port was named ControlCenter, which is a native macOS application. If this is happening to you, even if you use brute force (and kill) the application, it will restart itself. In my laptop, lsof -i :5000 returns that Control Center is being used by process id 433. I could do killall -p 433, but macOS keeps restarting the process.

The process running on this port turns out to be an AirPlay server. You can deactivate it in

System Preferences › Sharing, and unchecking AirPlay Receiver to release port 5000.

Check docker-compose.yml, it might be the case that the port is specified twice.

version: '3'services: registry: image: mysql:5.7 ports: - "3306:3306" <--- remove either this line or next - "127.0.0.1:3306:3306"

I had the same problem. I fixed this by stopping the Apache2 service on my host.

In your case it was some other process that was using the port and as indicated in the comments, sudo netstat -pna | grep 3000 helped you in solving the problem.

While in other cases (I myself encountered it many times) it mostly is the same container running at some other instance. In that case docker ps was very helpful as often I left the same containers running in other directories and then tried running again at other places, where same container names were used.

How docker ps helped me:

docker rm -f $(docker ps -aq) is a short command which I use to remove all containers.

Edit: Added how docker ps helped me.

In my case, the issue was that I was running the MongoDB as a root user, and stopping that did the trick.

sudo brew services stop mongodb-community

At first, make sure which service you are running in your specific port. In your case, you are already using port number 3000.

netstat -aof | findstr :3000

now stop that process which is running on specific port

lsof -i tcp:3000

Let me add one more case, because I had the same error and none of the solutions listed so far works:

serv1: ... networks: privnet: ipv4_address: 10.10.100.2 ...serv2: ... # no IP assignment, no dependencies networks: privnet: ipam: driver: default config: - subnet: 10.10.100.0/24

depending on the init order, serv2 may get assigned the IP 10.10.100.2 before serv1 is started, so I just assign IPs manually for all containers to avoid the error. Maybe there are other more elegant ways.

maybe it is too rude, but works for me. restart docker service itself

sudo service docker restart

hope it works for you also!

It makes more sense to change the port of the docker update instead of shutting down other services that use port 80.

When I run docker-compose up in my Docker project it fails with the following message:

Error starting userland proxy: listen tcp 0.0.0.0:3000: bind: address already in use

(Video) Docker Compose in 12 Minutes

netstat -pna | grep 3000

shows this:

tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN - 

I've already tried docker-compose down, but it doesn't help.