demyxsh
Demyx can not start after Docker Engine restarted.
Hi,
After restart docker engine, wp site was down, and the reason is that demyx_socket container did not started.
Running demyx command on terminal returned the following:
Starting demyx_socket ...
ERROR: for demyx_socket Cannot start service socket: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown
ERROR: for socket Cannot start service socket: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: process_linux.go:422: setting cgroup config for procHooks process caused: resulting devices cgroup doesn't match target mode: unknown
ERROR: Encountered errors while bringing up the project.
The only other container running on the same engine was Portainer. Running on CentOS7 Docker version 20.10.3, build 48d30b5
Ok, this error happened after updating CentOS7 with yum update.
The packages that yum updated:
===========================================================================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================================================================
Updating:
containerd.io x86_64 1.4.3-3.1.el7 docker-ce-stable 33 M
docker-ce x86_64 3:20.10.4-3.el7 docker-ce-stable 27 M
docker-ce-cli x86_64 1:20.10.4-3.el7 docker-ce-stable 33 M
docker-ce-rootless-extras x86_64 20.10.4-3.el7 docker-ce-stable 9.1 M
epel-release noarch 7-13 epel 15 k
libblkid x86_64 2.23.2-65.el7_9.1 updates 183 k
libgudev1 x86_64 219-78.el7_9.3 updates 109 k
libmount x86_64 2.23.2-65.el7_9.1 updates 185 k
libsmartcols x86_64 2.23.2-65.el7_9.1 updates 143 k
libuuid x86_64 2.23.2-65.el7_9.1 updates 84 k
net-snmp-libs x86_64 1:5.7.2-49.el7_9.1 updates 751 k
perl x86_64 4:5.16.3-299.el7_9 updates 8.0 M
perl-Pod-Escapes noarch 1:1.04-299.el7_9 updates 52 k
perl-libs x86_64 4:5.16.3-299.el7_9 updates 690 k
perl-macros x86_64 4:5.16.3-299.el7_9 updates 44 k
systemd x86_64 219-78.el7_9.3 updates 5.1 M
systemd-libs x86_64 219-78.el7_9.3 updates 418 k
systemd-sysv x86_64 219-78.el7_9.3 updates 97 k
tzdata noarch 2021a-1.el7 updates 501 k
util-linux x86_64 2.23.2-65.el7_9.1 updates 2.0 M
zlib x86_64 1.2.7-19.el7_9 updates 90 k
Transaction Summary
============================================================================================================================================================================================================================================
Right after this update, demyx_socket container goes down and the error message above mentioned is displayed.
Hi, sorry I didn't get back to you in IRC. It looks like you got it fixed by downgrading Docker. I will need to do more testing on CentOS or Rocky Linux as it's called now.
NP @demyxco The package that broke demyx_socket was docker-ce version 3:20.10.4-3.el7. I don't know why.
Hi, are you still getting this error? I believe CentOS is now deprecated and everyone should be moving to Rocky Linux. I'll keep testing on whatever version is still available in DigitalOcean.
I've not uptaded the system since then to not get this error anymore, so I'm not sure if it will break or not.
Ok I'll do some testing on both CentOS 7 and 8 since it's on there in DigitalOcean.
Closing this since it's been stale for a long time. Feel free to open a new issue.