# Port not available

**URL:** <https://forums.docker.com/t/port-not-available/99525>\
**Category:** General\
**Created:** [October 11, 2020, 4:40am UTC](https://forums.docker.com/t/port-not-available/99525 "2020-10-11T04:40:00Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dlstar88](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@dlstar88](https://forums.docker.com/u/dlstar88)\
**Post date:** [October 11, 2020, 4:40am UTC](https://forums.docker.com/t/port-not-available/99525/1 "2020-10-11T04:40:00Z")

</div>

When running EOS studio

 ![Screen Shot 2020-10-10 at 11.37.18 PM](https://global.discourse-cdn.com/docker/original/3X/2/b/2bee0b436f041c30b22235f04142a1935c66f383.png)

Concerned you can’t read the .png that I just sent, so here is the text from the instance:

docker run -dt --name eosio\_v2.0.5\_v2.0.5 --publish 8888:8888 --publish 5555:5555 --volume /Users/donniestarkey/.eosio/v2.0.5:/eosio -w /eosio eostudio/eos:v2.0.5 /bin/bash  
7698be1854dc0705be43100f071c95230f6c5175256bf63c096c26373df41dc3  
docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:8888: bind: address already in use.

I am a neub, and lost. Any direction would be helpful 🙂

Thanks,

---

<div class="post-metadata">

**Author:** ![tekki](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/tekki/32/21884_2.png) [@tekki](https://forums.docker.com/u/tekki)\
**Post date:** [October 11, 2020, 6:20am UTC](https://forums.docker.com/t/port-not-available/99525/2 "2020-10-11T06:20:02Z")

</div>

> [@dlstar88](#):
>
> Ports are not available: listen tcp 0.0.0.0:8888: bind: address already in use.

This means port 8888 is already occupied by another service. Could be a second container or an application that is running on the host.

---

<div class="post-metadata">

**Author:** ![dlstar88](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@dlstar88](https://forums.docker.com/u/dlstar88)\
**Post date:** [October 11, 2020, 12:14pm UTC](https://forums.docker.com/t/port-not-available/99525/3 "2020-10-11T12:14:54Z")

</div>

Thanks, is there a wiki, or tutorial to fix it?

---

<div class="post-metadata">

**Author:** ![tekki](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/tekki/32/21884_2.png) [@tekki](https://forums.docker.com/u/tekki)\
**Post date:** [October 11, 2020, 4:29pm UTC](https://forums.docker.com/t/port-not-available/99525/4 "2020-10-11T16:29:34Z")

</div>

There’s no wiki for that. You just have to find it and turn it off. I’ve no idea what system you are using, so it’s a bit difficult to give an advice. Maybe you could call `http://localhost:8888` in your browser to find out more.  
Another way would be to publish to another port, for example `--publish 8877:8888` (left number is port on the host, right in the container).

---

<div class="post-metadata">

**Author:** ![dlstar88](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@dlstar88](https://forums.docker.com/u/dlstar88)\
**Post date:** [October 11, 2020, 9:11pm UTC](https://forums.docker.com/t/port-not-available/99525/5 "2020-10-11T21:11:43Z")

</div>

> [@tekki](#):
>
> [http://localhost:8888](http://localhost:8888)

Thanks for the reply. I am using a Mac (Catalina). I pasted “[http://localhost:8888](http://localhost:8888)” into the address bar for both safari and brave, but neither could not open the page. I also typed “–publish 8877:8888” into the address bars, which didn’t work either.

I also checked my activity monitor. The port is not mentioned there as being used.

---

<div class="post-metadata">

**Author:** ![tekki](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/tekki/32/21884_2.png) [@tekki](https://forums.docker.com/u/tekki)\
**Post date:** [October 12, 2020, 6:24am UTC](https://forums.docker.com/t/port-not-available/99525/6 "2020-10-12T06:24:17Z")

</div>

I’m not a Mac user, so I can’t give you specific help for Mac OS. With `–publish 8877:8888` I meant that you should modify the start command of the container.  
Did you already check if other containers are running or if the one you want to start here is running already? `docker container ls`, or `docker container ls -a` to list the stopped containers too. You call `docker run -d`, this means you start the container as daemon (in the background).