Created attachment 850861 [details] patch to move lock file from /var/run to /run Description of problem: When a minimal container is installed with yum --installroot=$container, $container/var/run is not a symlink to ../run as it should be, but a directory. The sequence of events that leads to this is such: 1. filesystem package has /var/run as %ghost, and creates /var/run symlink in %pretrans, because of rpm's issues with converting a directory to a symlink 2. yum creates a file in /var/run 3. when filesystem is installed, the directory already exists and the symlink is not created. Note that some packages contain or create files in /var/run, but they are installed later, so this is not a problem. yum seems to be culprit here. As a result of this, created $container is unusable, e.g. the dbus socket is created as /var/run/dbus/system_bus_socket, but some programs look for it in /run/dbus/. Version-Release number of selected component (if applicable): yum-3.4.3-121.fc20.noarch filesystem-3.2-19.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. sudo yum -y --releasever=20 --installroot=`pwd`/container --disablerepo='*' --enablerepo=fedora install systemd passwd yum fedora-release vim-minimal procps-ng 2. when the package installation starts, press ^Z after the first few packages 3. container/var/run contains only var/run/yum.pid, where the contents match the stopped yum, and var/run is a directory
This might be the same: https://bugzilla.redhat.com/show_bug.cgi?id=975864
Yeah, even the patch is the same :) I should have looked properly. *** This bug has been marked as a duplicate of bug 975864 ***