# ./launcher rebuild app Port is already allocated

**URL:** https://meta.discourse.org/t/launcher-rebuild-app-port-is-already-allocated/30006
**Category:** Support
**Created:** [2015 年 6 月 14 日午後 8:16 UTC](https://meta.discourse.org/t/launcher-rebuild-app-port-is-already-allocated/30006 "2015-06-14T20:16:55Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![tuttle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tuttle/32/34114_2.png) [@tuttle](https://meta.discourse.org/u/tuttle)
#### Post date: [2015 年 6 月 14 日午後 8:16 UTC](https://meta.discourse.org/t/launcher-rebuild-app-port-is-already-allocated/30006/1 "2015-06-14T20:16:55Z")

</div>

Hi,

I’ve just tried to upgrade the docker image with the commanfs suggested by @sam

cd /var/discourse/  
git pull  
./launcher rebuild app

Unfortunately the whole process ends with  
Cannot start container app: Bind for 0.0.0.0:2222 failed: port is already allocated

And my forum is offline ☹  
netstat -lptu doesn’t show any processes using that port.

Any help out there please?

---

<div class="post-metadata">

### Author: ![tuttle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tuttle/32/34114_2.png) [@tuttle](https://meta.discourse.org/u/tuttle)
#### Post date: [2015 年 6 月 14 日午後 8:23 UTC](https://meta.discourse.org/t/launcher-rebuild-app-port-is-already-allocated/30006/2 "2015-06-14T20:23:07Z")

</div>

I just tried ‘service docker restart’ and the forum is back on line. 🙂

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2015 年 6 月 15 日午前 12:31 UTC](https://meta.discourse.org/t/launcher-rebuild-app-port-is-already-allocated/30006/3 "2015-06-15T00:31:37Z")

</div>