# Docker problem after machine restart

**URL:** <https://meta.discourse.org/t/docker-problem-after-machine-restart/33604>\
**Category:** Product Support\
**Created:** [September 22, 2015, 6:48pm UTC](https://meta.discourse.org/t/docker-problem-after-machine-restart/33604 "2015-09-22T18:48:27Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![clay](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/clay/32/102156_2.png) [@clay](https://meta.discourse.org/u/clay)\
**Post date:** [September 22, 2015, 6:48pm UTC](https://meta.discourse.org/t/docker-problem-after-machine-restart/33604/1 "2015-09-22T18:48:27Z")

</div>

I had to reboot the machine I have Discourse running on to replace a bad graphics card. However, Discourse won’t restart. When I try `./launcher restart app` from within `/var/discourse`, I see:

```plaintext
clay@machine:/var/discourse$ ./launcher restart app
+ /usr/bin/docker stop -t 10 app
app

starting up existing container
+ /usr/bin/docker start app
Error response from daemon: Cannot start container app: Bind for 0.0.0.0:9999 failed: port is already allocated
Error: failed to start containers: [app]

```

When I `docker ps -a` it looks like:

```plaintext
clay@machine:/var/discourse$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1784278bfaa7 local_discourse/app "/sbin/boot" 4 weeks ago Exited (143) 18 minutes ago app                 
fdfe02391dc0 local_discourse/app "/sbin/runit" 12 months ago Up 10 minutes 0.0.0.0:2222->22/tcp, 0.0.0.0:9999->80/tcp tender_mayer        
72e1859eb261 hello-world "/hello" 12 months ago Exited (0) 12 months ago hopeful_kirch 

```

That sort of makes it look like an old version of Discourse is running?

What’s going on here? How can I get Discourse up and running again? All was fine before I shut down and rebooted.

---

_[View the full topic](https://meta.discourse.org/t/docker-problem-after-machine-restart/33604)._