[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?

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.

[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)

[image] 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: [image] 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?

[image] mpalmer: /usr/bin/docker.io run -it --rm busybox sh [root@xxx ~]# /usr/bin/docker.io run -it --rm busybox sh / # No errors

“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.

They are symlinked. /usr/bin/docker.io start app gives the same error as ./launcher start app.

Isn’t it great how Docker makes everything so much easier…

[image] mntbighker: Storage Driver: devicemapper You are using devicemapper, and this isn’t what we recommend as a storage drive, so keep that in mind.

Container fails startup after yum update

Product Support

mntbighker (Mark Moorcroft) February 2, 2017, 12:43am 9

I had to rebuild, but now it works.

Thanks

Topic		Replies	Views
Container fails to (re)start after system update Self-hosting	7	2190	June 10, 2016
Can't run ./launcher rebuild app - Docker storage driver is unsupported Product Support	71	13929	August 26, 2019
Your Docker installation is not working correctly after running launcher rebuild app Self-hosting	6	1535	February 16, 2019
Device 'docker0' missing after system upgrade? Self-hosting	26	5508	December 22, 2016
New installation on Fedora 23 - FAILED RuntimeError: cd /var/www/discourse && su discourse -c Self-hosting	17	2803	March 21, 2016

Container fails startup after yum update

Related topics