Bug 1393312

Summary: Upgrade to oci-systemd-hook-0.1.4-7.gita9c551a.el7.x86_64 breaks systemd containers
Product: Red Hat Enterprise Linux 7 Reporter: Jan Pazdziora <jpazdziora>
Component: oci-systemd-hookAssignee: Mrunal Patel <mpatel>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Jenner <mjenner>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: fkluknav, jpazdziora, mpatel, qcai
Target Milestone: rcKeywords: Extras, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-23 15:40:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jan Pazdziora 2016-11-09 10:12:15 UTC
Description of problem:

With the following Dockerfile

FROM rhel7
ENV container docker
ENTRYPOINT [ "/usr/sbin/init" ]

running the container via

docker run --rm -ti --name systemd-hook-container systemd-hook

with

docker-1.12.3-4.el7.x86_64
oci-systemd-hook-0.1.4-6.git337078c.el7.x86_64

works.

Alas, upgrading to oci-systemd-hook-0.1.4-7.gita9c551a.el7.x86_64 breaks the setup.

Version-Release number of selected component (if applicable):

oci-systemd-hook-0.1.4-7.gita9c551a.el7.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have systemd-hook/Dockerfile shown above.
2. Build container image: docker build -t systemd-hook systemd-hook
3. Run container: docker run --rm -ti --name systemd-hook-container systemd-hook

Actual results:

systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Detected virtualization docker.
Detected architecture x86-64.

Welcome to Red Hat Enterprise Linux Server 7.3 (Maipo)!

Set hostname to <bc1da43aa1dc>.
Failed to install release agent, ignoring: No such file or directory
Failed to create root cgroup hierarchy: Read-only file system
Failed to allocate manager object: Read-only file system
[!!!!!!] Failed to allocate manager object, freezing.
Error response from daemon: No such container: bc1da43aa1dc7d34cb3fc614eaa72617f9e6292b48abb13d1681579b41bfa215
Error response from daemon: devmapper: Unknown device 914d90005e813b6fb5d357cb6d8ab808df606b47917459ffe0387c562db869a4

Expected results:

# docker run --rm -ti --name systemd-hook-container systemd-hook
systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Detected virtualization docker.
Detected architecture x86-64.

Welcome to Red Hat Enterprise Linux Server 7.3 (Maipo)!

Set hostname to <9dd80e7f2840>.
[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Created slice system-getty.slice.
         Starting Journal Service...
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
         Starting Load/Save Random Seed...
[...]

Additional info:

Downgrade to oci-systemd-hook-0.1.4-6.git337078c.el7.x86_64 fixes the problem.

Comment 2 Mrunal Patel 2016-11-16 18:35:57 UTC
Created a PR for the fix here.

Comment 5 Jan Pazdziora 2016-12-21 08:54:22 UTC
*** Bug 1406674 has been marked as a duplicate of this bug. ***

Comment 6 Jan Pazdziora 2016-12-21 08:54:58 UTC
Fixing status. This has bitten me again.

Comment 8 Qian Cai 2017-02-23 15:40:17 UTC
Already fixed in 7.3.2 (oci-systemd-hook-0.1.4-9.git671c428.el7).