Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Docker error “bind: address already in use” – How to resolve

by | May 7, 2021

Stuck with the Docker error “bind: address already in use”? We can help you.

Recently, we had a customer who came across this error when he tried to start a docker instance.

As part of our Docker Hosting services, we assist our customers with several Docker queries.

Today, let us see how to resolve this error.


Docker error “bind: address already in use”

While trying to start a docker instance, one of our customers came across the below error:

Error response from daemon: Cannot start container: listen tcp bind: address already in use

The major cause of this error can be another process using the same port.



1. To start the container successfully, we kill whatever is using the port.

Initially, we check what uses the port. If it is non-essential at this time, we kill it.

sudo lsof -i tcp:8080

In the prompt for the device password, we type it in and press enter. We can replace 8080 with whichever port we want.

Then, we will get a list of currently running processes. Look at the PID of the process. We need it to issue the kill command.

We need to find the process that is obstructing the desired port and ensure it is not of our need.

Then we run the below command to stop the process:

# sudo kill -9 PID
2. Change to another port by modifying the default port in the docker-compose.yml file.

However, if the process that uses the desired port is essential for our setup, we have to change the port for the docker instance.

Ensure to adjust any other project settings linking to this particular port to the new value we select.

Restart the container instance after doing this for changes to take effect.

To start a Docker container using a different port, our Support Techs suggest the steps below:

  • We find a free TCP port that we can use (for example, 8086)
  • Then we delete the existing container:
    docker rm docker_name

    When Docker creates a container, it assigns the ports to it. To change the ports, we delete the existing container first, then re-create it.

  • Finally, we restart with a different host port number, for example:
    docker run -d -p 8086:8080 -p 55555:55555 -p:80:80 –shm-size=2g –env username_admin_globalaccesslevel=admin –env username_admin_password=admin –name=docker_name solace/solace-pubsub-standard
3. If for any reason our host reboots.

This issue can happen when the host reboots.

In such a case, we restart our apache server. Stopping the apache2 service in the host can solve it.

$ sudo /etc/init.d/apache2 restart
$ sudo apachectl -k restart
4. If Nginx is running globally, it can be the reason too.
$ sudo nginx -s stop

This can happen when the same container runs at some other instance. In that case, docker ps is very helpful.

docker-compose down # Stop container on the current directory if there is a docker-compose.yml
docker rm -fv $(docker ps -aq) # Remove all containers
sudo lsof -i -P -n | grep <port number> # List who is using the port

[Need help with the resolution? We’d be happy to assist]



In short, we saw the methods our Support Techs employ in order to fix the Docker error “bind: address already in use”.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *



Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.