At the moment I’m getting message "no response from daemon: shim error; docker.runc not installed on system". I tried a possible solution for that to no avail Earlier today I installed telnet (which I guess updated yum?) to troubleshoot an email issue. Right now, I’m kinda hosed. I’m on Centos 7 I believe. Initially docker would not start, stated a problem with the network bridge. Removed and installed docker from yum to get that working again. Here’s my docker.info at present: [image] Containers = 0 kinda concerns me, although I did make a backup of my docker directory before messing around. I did run docker rm app at one point (After the error about docker-runc occured)… maybe not such a good idea. Attempt to rebuild results in same error message regarding docker-runc

Hmmm. It seems that docker is actually a script which performs a lookup for possible paths. But only on RHEL/CentOS 7 where this comes from the RHEL repositories. I don’t have /usr/bin/docker-current here. [root@icinga2 ~]# docker -v Docker version 17.12.0-ce, build c97c6d6 [root@icinga2 ~]# ps aux | grep docker root 20688 0.9 1.9 542268 35964 ? Ssl 20:56 0:37 /usr/bin/dockerd root 20693 0.7 1.2 366356 22872 ? Ssl 20:56 0:29 docker-containerd --config /var/run/docker/containerd/containerd.toml root 29081 0.0 0.0 112668 944 pts/0 S+ 22:05 0:00 grep --color=auto docker Systemd starts dockerd here, you can see that from the service file in /lib/systemd/system/docker.service: [Unit] Description=Docker Application Container Engine Documentation=https://docs.docker.com After=network-online.target firewalld.service Wants=network-online.target [Service] Type=notify # the default is not to use systemd for cgroups because the delegate issues still # exists and systemd currently does not support the cgroup feature set required # for containers run by docker ExecStart=/usr/bin/dockerd ExecReload=/bin/kill -s HUP $MAINPID # Having non-zero Limit*s causes performance problems due to accounting overhead # in the kernel. We recommend using cgroups to do container-local accounting. LimitNOFILE=infinity LimitNPROC=infinity LimitCORE=infinity # Uncomment TasksMax if your systemd version supports it. # Only systemd 226 and above support this version. #TasksMax=infinity TimeoutStartSec=0 # set delegate yes so that systemd does not reset the cgroups of docker containers Delegate=yes # kill only the docker process, not all processes in the cgroup KillMode=process # restart the docker process if it exits prematurely Restart=on-failure StartLimitBurst=3 StartLimitInterval=60s [Install] WantedBy=multi-user.target Do you have any other occurrences of a Systemd service file for docker, e.g. in /etc/systemd? Anyhow, I’d suggest to start “fresh”. Purge anything which has docker in its name from the system yum remove docker \ docker-common \ docker-selinux \ docker-engine find /etc/systemd -name '*docker*' -exec rm -f {} \; find /lib/systemd -name '*docker*' -exec rm -f {} \; and go for installing it using this guide again.

As long as you’ve got a recent backup, you should be good to go. Actually, you could even just rsync /var/discourse to the new server and rebuild.

I have back up from yesterday on S3. But rsync would probably be better so I have all the content until things went south.

If systemd says “disabled”, you have multiple options systemctl enable docker SELinux is causing fun this is a meta unit which is disabled. The real service is named differently. You can see that for example with Elasticsearch, where the service unit files are named differently for each cluster instance. Let’s do this in a CentOS Vagrant VM (actually, it is icinga-vagrant/icinga2x with a stopped httpd) [image] Install Docker Engine on CentOS Learn how to install Docker Engine on CentOS. These instructions cover the different installation methods, how to uninstall, and next steps. yum install -y yum-utils \ device-mapper-persistent-data \ lvm2 yum-config-manager \ --add-repo \ https://download.docker.com/linux/centos/docker-ce.repo yum -y install docker-ce systemctl enable docker.service systemctl start docker.service git clone https://github.com/discourse/discourse_docker /var/discourse cd /var/discourse ./discourse-setup Bootstrap afterwards works then. [root@icinga2 discourse]# ./launcher bootstrap app which: no docker.io in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/root/bin) WARNING: We are about to start downloading the Discourse base image This process may take anywhere between a few minutes to an hour, depending on your network speed Please be patient This also works for me with setenforce 1 as the Docker package installs an SELinux policy. So this somehow seems to be related to the missing enable/start step on CentOS. No need for a migration run to Ubuntu imho.

Thanks. So removed an installed docker-ce again per the guide above, ran “systemctl enable docker.service” but it still fails to start when I try to start it from systemctrl I’m getting a little more information this time under journalctrl… "Failed at step EXEC spawning usr/bin/docker-current: no such file or directory. [CouldNotAddDependencyForFS]

I’d appreciate copy pasted logs, so everyone can copy them into Google too. Screenshots are really hard to re-type. Please run docker -v to show the current version. To me it seems you still have the old system’s docker installed side-by-side (the linked setup docs tell you how to remove that beforehand).

[image] dnsmichi: I’d appreciate copy pasted logs, so everyone can copy them into Google too. Screenshots are really hard to re-type. I understand. The (web) VNC client I’m using doesnt seem to support copy and paste and my local VNC client doesnt seem to connect.. Ill try again though Docker version displays as 17.12.0-ce, build c97c6d6

[image] dnsmichi: find /etc/systemd -name '*docker*' -exec rm -f {} \; find /lib/systemd -name '*docker*' -exec rm -f {} \; This appears to be the key. I did go though and remove as many docker-xxx packages as I could think of earlier, and it made no difference. This time, docker installed and started after I ran the find lines. Discourse is updating it’s base now… We’ll she I was (still am) pondering moving to ubuntu purely because my exisitng setup on centos seems to be very fragile. Anytime I try to update discourse, I end up with a broken container, or a docker that won’t start.

[image] SouperC: I was (still am) pondering moving to ubuntu purely because my exisitng setup on centos seems to be very fragile. Anytime I try to update discourse, I end up with a broken container, or a docker that won’t start. If I’m reading this thread correctly, I’m pretty sure you’d have spent much less time if you’d moved to Ubuntu.

[image] pfaffman: If I’m reading this thread correctly, I’m pretty sure you’d have spent much less time if you’d moved to Ubuntu Probably :smile: Although I would had to move all my data across and I’m not sure how involved that would be. I was doing both really. Alternating between working on ubuntu and this centos install. Hit a snag with docker under ubuntu on the same hosting. Went through signup process with another host, docker and discourse was simple, but email with sendgrid is not co-operating for some reason Thanks everyone for your help.

Some mail service I dealt with lately restricted access by IP so I had to provide the discourse server address to the mail service.

Docker shim error on CentOS 7

Product Support

pfaffman (Jay Pfaffman) January 11, 2018, 12:29am 16

If I’m reading this thread correctly, I’m pretty sure you’d have spent much less time if you’d moved to Ubuntu.

Topic		Replies	Views
Can't run the launcher to install Discourse on CentOS 7 Self-hosting	25	11942	August 23, 2017
I can't start discourse on CentOS Self-hosting	7	2479	May 12, 2017
Installation failing on CentOS 7.3 Product Support	9	3853	March 2, 2017
Installation fails on my Debian server Self-hosting	24	2697	March 18, 2019
Device "docker0" does not exist Self-hosting	36	21080	April 10, 2019

Docker shim error on CentOS 7

Related topics