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:

On RHCOS (based on RHEL 8.1) I'm doing a container build on startup
and I see a ton of messages in the logs that are mostly not useful:

```
[  OK  ] Created slice libcontainer_29015_systemd_test_default.slice.                                                                                                      
[  OK  ] Removed slice libcontainer_29015_systemd_test_default.slice.
```

This is how many times I see it for one container build:

```
# journalctl | grep 'slice libcontainer_' | wc -l 
3494
```


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

# rpm -q podman systemd
podman-1.6.2-0.3.gita8993ba.el8.x86_64
systemd-239-18.el8.x86_64


How reproducible:

Seems pretty reliable.


Steps to Reproduce:
1. Boot RHCOS/RHEL
2. Do a container build
3. Watch journalctl

If it helps I'm doing container builds of https://github.com/dustymabe/kvc-simple-kmod.git

Should be fixed by https://github.com/opencontainers/runc/pull/2117

We should ship the runc that is being shipped in Fedora 30,31

runc-1.0.0-61.rc9.el8 is now part of container-tools-rhel8-8.2.0.

Dusty any chance you could try runc-1.0.0-61.rc9.el8 and see if it cures your ills?

(In reply to Tom Sweeney from comment #8)
> Dusty any chance you could try runc-1.0.0-61.rc9.el8 and see if it cures
> your ills?

Yep seems to resolve the problem.

Awesome, thanks for the test Dusty(In reply to Dusty Mabe from comment #10)
> (In reply to Tom Sweeney from comment #8)
> > Dusty any chance you could try runc-1.0.0-61.rc9.el8 and see if it cures
> > your ills?
> 
> Yep seems to resolve the problem.

Awesome, thanks for the test Dusty.

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/RHSA-2020:1650