# Container fails to (re)start after system update
**URL:** https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541
**Category:** Self-hosting
**Created:** [June 10, 2016, 7:54pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541 "2016-06-10T19:54:41Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@JohnDoe1](https://meta.discourse.org/u/JohnDoe1)
#### Post date: [June 10, 2016, 7:54pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/1 "2016-06-10T19:54:41Z")
Hi,
I upgraded my server (debian 8.5) a few days ago via apt-get. docker-engine was updated. I use docker only for discourse. The discourse container did not restart after updating. Manually restarting fails with
> /var/discourse# ./launcher restart app
> /usr/bin/docker: Error response from daemon: rpc error: code = 2 desc = “shim error: invalid argument”.
> Your Docker installation is not working correctly
> See: [Troubleshoot docker installation issues](https://meta.discourse.org/t/docker-error-on-bootstrap/13657/18)
The link provided does not help or I don’t understand. I found some threads around here and tried
> /var/discourse# git pull
> ./launcher rebuild app
but this failed with the same result.
Thanks for any help on how to fix or debug this.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 10, 2016, 8:05pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/2 "2016-06-10T20:05:25Z")
What does `docker version` and `docker info` report? Docker needs to be installed, ideally updated to latest, and working.
---
### Author:  [@JohnDoe1](https://meta.discourse.org/u/JohnDoe1)
#### Post date: [June 10, 2016, 8:09pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/3 "2016-06-10T20:09:33Z")
docker version
```
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:39 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 21:23:39 2016
OS/Arch: linux/amd64
```
docker info
```
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 27
Server Version: 1.11.2
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 38
Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 3.2.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 997.1 MiB
Name: vadmin1234
ID: Tdontknowifthisshouldbeprivate
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
```
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 10, 2016, 8:12pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/4 "2016-06-10T20:12:15Z")
Hmm, not sure. That looks roughly correct, but clearly something is not right with your Docker. Maybe remove Docker and re-install?
---
### Author:  [@JohnDoe1](https://meta.discourse.org/u/JohnDoe1)
#### Post date: [June 10, 2016, 8:51pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/5 "2016-06-10T20:51:08Z")
did not help. same issue ☹
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 10, 2016, 8:53pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/6 "2016-06-10T20:53:47Z")
Are you on bare metal or some kind of hidden VM? I’ve heard horror stories from being on shared VPSes using certain types of cheap virtualization with Docker.. it just doesn’t work.
---
### Author:  [@JohnDoe1](https://meta.discourse.org/u/JohnDoe1)
#### Post date: [June 10, 2016, 9:03pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/7 "2016-06-10T21:03:58Z")
I am not sure. The server is definetly just a virtual machine but I did not feel any restraints so far and discourse was working nicely for some months now just like some other (non docker) apps, that still work fine.
Meanwhile I also did
> rebuild app
again after re installing docker. So now it should be all fresh, or is there anything else I could try to reset (without losing data)?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 10, 2016, 9:04pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/8 "2016-06-10T21:04:37Z")
Nope, without a functioning Docker you are pretty hosed.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:45pm UTC](https://meta.discourse.org/t/container-fails-to-re-start-after-system-update/45541/9 "2024-06-08T12:45:37Z")
This topic was automatically closed after 2919 days. New replies are no longer allowed.