# Container fails startup after yum update
**URL:** https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755
**Category:** Support
**Created:** [February 1, 2017, 10:17pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755 "2017-02-01T22:17:19Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 1, 2017, 10:17pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/1 "2017-02-01T22:17:19Z")
```
[root@xxx /var/discourse]# ./launcher start app
starting up existing container
+ /usr/bin/docker.io start app
Error response from daemon: shim error: docker-runc not installed on system
Error: failed to start containers: app
Linux xxx.gov 3.10.0-514.6.1.el7.x86_64 #1 SMP Wed Jan 18 13:06:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
```
I can however start a new container “docker run -it --rm busybox sh” with no errors.
Ideas?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 1, 2017, 10:37pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/2 "2017-02-01T22:37:03Z")
What does `docker info` prints?
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 1, 2017, 11:19pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/3 "2017-02-01T23:19:29Z")
```
[root@xxx ~]# docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 38
Server Version: 1.12.5
Storage Driver: devicemapper
Pool Name: vg_alder_main-docker--pool
Pool Blocksize: 524.3 kB
Base Device Size: 107.4 GB
Backing Filesystem: xfs
Data file:
Metadata file:
Data Space Used: 15.88 GB
Data Space Total: 28.5 GB
Data Space Available: 12.63 GB
Metadata Space Used: 3.076 MB
Metadata Space Total: 67.11 MB
Metadata Space Available: 64.03 MB
Thin Pool Minimum Free Space: 2.85 GB
Udev Sync Supported: true
Deferred Removal Enabled: true
Deferred Deletion Enabled: true
Deferred Deleted Device Count: 0
Library Version: 1.02.135-RHEL7 (2016-11-16)
Logging Driver: json-file
Cgroup Driver: systemd
Plugins:
Volume: local
Network: host bridge null overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Security Options: seccomp
Kernel Version: 3.10.0-514.6.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 2
Total Memory: 3.86 GiB
Name: alder.ndc.nasa.gov
ID: 4HCD:CXPT:UOD3:TH6S:6CZ3:XOEV:FYIF:GHBZ:OCIR:JBTX:UVG6:G37X
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Insecure Registries:
127.0.0.0/8
Registries: docker.io (secure)
```
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [February 1, 2017, 11:48pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/4 "2017-02-01T23:48:44Z")
> [@mntbighker](#):
>
> I can however start a new container “docker run -it --rm busybox sh” with no errors.
You’re not running the same Docker binary as `./launcher` is:
> [@mntbighker](#):
>
> starting up existing container
>
> - /usr/bin/docker.io start app
What happens if you try to run `/usr/bin/docker.io run -it --rm busybox sh`?
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 1, 2017, 11:52pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/5 "2017-02-01T23:52:00Z")
> [@mpalmer](#):
>
> /usr/bin/docker.io run -it --rm busybox sh
> [root@xxx ~]# /usr/bin/docker.io run -it --rm busybox sh
> / #
No errors
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [February 1, 2017, 11:55pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/6 "2017-02-01T23:55:32Z")
> “Curiouser and curiouser!” cried Alice (she was so much surprised, that for the moment she quite forgot how to speak good English).
What about `/usr/bin/docker.io start app`? Also, does `docker.io info` give different results to `docker info`? Are they symlinked, or at least provided by the same RPM? If they’re in different RPMs, try removing the older one (it _should_ be the one providing `docker.io`, because that’s a legacy name), and see if `./launcher` becomes infinitely happier.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 2, 2017, 12:07am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/7 "2017-02-02T00:07:25Z")
They are symlinked.
/usr/bin/docker.io start app gives the same error as ./launcher start app.
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [February 2, 2017, 12:27am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/8 "2017-02-02T00:27:38Z")
Oooooh… have you done a `./launcher rebuild app`? Or at least a `docker rm app`? Try the latter first, and if that still doesn’t work, give the former a shot.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 2, 2017, 12:43am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/9 "2017-02-02T00:43:52Z")
I had to rebuild, but now it works.
Thanks
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [February 2, 2017, 12:44am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/10 "2017-02-02T00:44:40Z")
Isn’t it great how Docker makes everything so much easier…
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 2, 2017, 12:47am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/11 "2017-02-02T00:47:33Z")
Right… sooo much
:mdr:
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 2, 2017, 12:47am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/12 "2017-02-02T00:47:34Z")
> [@mntbighker](#):
>
> Storage Driver: devicemapper
You are using devicemapper, and this isn’t what we recommend as a storage drive, so keep that in mind.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [February 2, 2017, 12:49am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/13 "2017-02-02T00:49:09Z")
Thanks, note to self.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 2, 2017, 2:29am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/14 "2017-02-02T02:29:04Z")
You will experience drive corruption with devicemapper, it is just a matter of time. We block installs if devicemapper is detected.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [March 6, 2017, 8:14pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/15 "2017-03-06T20:14:29Z")
Is this something you see as a permanent problem, or will later OS versions possibly allow reliable devmapper? Is it open bugs?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 6, 2017, 8:15pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/16 "2017-03-06T20:15:01Z")
Devicemapper is not stable in our experience, so we don’t support it.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [June 20, 2017, 2:40am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/17 "2017-06-20T02:40:53Z")
I’m wondering if that is an over simplified policy? Today turned ugly when I tried to update Discourse. It said I needed to update Docker. I was reminded that I never switched devmapper from loop mode to direct-lvm. According to the Docker site devmapper direct-lvm is the recommended method on Redhat and CentOS. Because AUFS is not supported. Now I have to use --skip-prereqs using the Docker recommended storage driver. Is the default loop mode actually the problem because people never do the xtra steps to direct-lvm (block level)?
```plaintext
> [root@xxxx ~]# docker info
> Containers: 2
> Running: 0
> Paused: 0
> Stopped: 2
> Images: 39
> Server Version: 1.12.6
> Storage Driver: devicemapper
> Pool Name: docker-thinpool
> Pool Blocksize: 524.3 kB
> Base Device Size: 10.74 GB
> Backing Filesystem: xfs
> Data file:
> Metadata file:
> Data Space Used: 490.7 MB
> Data Space Total: 490.7 MB
> Data Space Available: 0 B
> Metadata Space Used: 122.9 kB
> Metadata Space Total: 4.194 MB
> Metadata Space Available: 4.071 MB
> Thin Pool Minimum Free Space: 48.76 MB
> Udev Sync Supported: true
> Deferred Removal Enabled: true
> Deferred Deletion Enabled: true
> Deferred Deleted Device Count: 0
> Library Version: 1.02.135-RHEL7 (2016-11-16)
> Logging Driver: json-file
> Cgroup Driver: systemd
> Plugins:
> Volume: local
> Network: host bridge null overlay
> Swarm: inactive
> Runtimes: docker-runc runc
> Default Runtime: docker-runc
> Security Options: seccomp
> Kernel Version: 3.10.0-514.10.2.el7.x86_64
> Operating System: CentOS Linux 7 (Core)
> OSType: linux
> Architecture: x86_64
> Number of Docker Hooks: 2
> CPUs: 2
> Total Memory: 3.86 GiB
> Name: xxxx
> ID: 4HCD:CXPT:UOD3:TH6S:6CZ3:XOEV:FYIF:GHBZ:OCIR:JBTX:UVG6:G37X
> Docker Root Dir: /var/lib/docker
> Debug Mode (client): false
> Debug Mode (server): false
> Registry: https://index.docker.io/v1/
> Insecure Registries:
> 127.0.0.0/8
> Registries: docker.io (secure)
```
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [June 20, 2017, 6:25am UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/18 "2017-06-20T06:25:00Z")
Devicemapper in general was a dumpster fire for a long, long time. It may be that these days dm+loop is still bad but dm+lvm is OK, but… once bitten and all that.
---
### Author:  [@mntbighker](https://meta.discourse.org/u/mntbighker)
#### Post date: [June 20, 2017, 11:00pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/19 "2017-06-20T23:00:22Z")
Yesterday I had to drop to command line to update Discourse. This was the first time seeing the need to start using --ignore-prereqs. Will the web based updater fail from now on?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [June 20, 2017, 11:02pm UTC](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755/20 "2017-06-20T23:02:27Z")
> [@mntbighker](#):
>
> Will the web based updater fail from now on?
The web based updated will ask for a command line rebuild every time we make a change that depends on new OS level software, like updated nginx, ruby, postgresql, etc.
We upgrade database every two years, and ruby almost every year, for reference.
[Next page](https://meta.discourse.org/t/container-fails-startup-after-yum-update/56755.md?page=2)