RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
# docker run -d  rhel7 init
# ausearch -m AVC----
time->Wed Apr  5 16:36:37 2017
type=SYSCALL msg=audit(1491424597.983:276): arch=c000003e syscall=165 success=no exit=-13 a0=55f7275fcad2 a1=55f7275f8ce0 a2=55f7275fcad2 a3=100002f items=0 ppid=13067 pid=13086 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd" exe="/usr/lib/systemd/systemd" subj=system_u:system_r:svirt_lxc_net_t:s0:c11,c931 key=(null)
type=AVC msg=audit(1491424597.983:276): avc:  denied  { remount } for  pid=13086 comm="systemd" scontext=system_u:system_r:svirt_lxc_net_t:s0:c11,c931 tcontext=system_u:object_r:svirt_sandbox_file_t:s0:c11,c931 tclass=filesystem

This is working fine with released 7.3.3 version - (oci-systemd-hook-0.1.4-9.git671c428.el7), and broken since oci-systemd-hook-0.1.4-10.git0c91618.el7.x86_64.rpm as well as the version in 7.3.4 (oci-systemd-hook-0.1.7-1.git1788cf2.el7.x86_64).

Version-Release number of selected component (if applicable):
RHEL/Atomic Host 7.3.4

How reproducible:
always

Actually, oci-systemd-hook-0.1.4-9.git671c428.el7 is also working fine. The bisect indicated the first bad commit is a8f577c51d851b0a15907ebbc2fbec4b9f2208ab in the upstream repo.

does "sudo audit2allow -a" help?

# audit2allow -a
#============= svirt_lxc_net_t ==============
allow svirt_lxc_net_t svirt_sandbox_file_t:filesystem { remount unmount };

On the side node, this reminds me that the umount was probably triggered by
https://bugzilla.redhat.com/show_bug.cgi?id=1439370

The 2 bugs are probably not related though.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0949