Docker Yum installation Error service start error

A similar error occurred while using the Docker container Yum installation:

Transaction Check Error:
file/usr/lib64/libsystemd-daemon.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package Sy Stemd-container-libs-208.20-6.el7.centos.x86_64
file/usr/lib64/libsystemd-id128.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package sys Temd-container-libs-208.20-6.el7.centos.x86_64
file/usr/lib64/libsystemd-journal.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package s Ystemd-container-libs-208.20-6.el7.centos.x86_64
file/usr/lib64/libsystemd-login.so.0 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package sys Temd-container-libs-208.20-6.el7.centos.x86_64
File/usr/lib64/libudev.so.1 from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package Systemd-cont Ainer-libs-208.20-6.el7.centos.x86_64
File/usr/lib64/security/pam_systemd.so from install of systemd-libs-219-19.el7.x86_64 conflicts with file from package s Ystemd-container-libs-208.20-6.el7.centos.x86_64

This is due to the transition from the systemd-container * package to the actual systemd. For some reason, the upstream package is still in conflict, so you will have an error installing the package. The solution is to get the latest CentOS image. or execute the command:

Yum install-y libsystemd-daemon.so.0 libsystemd-id128.so.0 libsystemd-journal.so.0 libsystemd-login.so.0 libudev.so .1 Systemd-container-libs

Only wish you good luck.

Another thing that happens when you start a service in a Docker container:

Failed to get D-bus connection:operation not permitted

First of all congratulations on using the CENTOS7 image, and then unfortunately tell you that this problem is a bug will be resolved in centos7.2.

What you can do now is to start it in a different way. Or swap with CENTOS6 's image.

Currently, SYSTEMD in CentOS 7 have been removed and replaced with a FAKESYSTEMD package for dependency resolution. This was due to systemd requiring the cap_sys_admin capability, as well as being able to read the host ' s cgroups. If you wish to replace the FAKESYSTEMD package and use systemd normally, please follow the steps below.

This article from "New One" blog, declined reprint!

Docker Yum installation Error service start error