Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Seems related to: https://github.com/containers/buildah/issues/2168
(or is very similar)

When we run `mock -r fedora-35-x86_64 --shell`, DNF process in
`podman run` fails with:
```
Fedora 35 - x86_64                              0.0  B/s |   0  B     00:00    
Errors during downloading metadata for repository 'fedora':
  - Curl error (6): Couldn't resolve host name for https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64 [getaddrinfo() thread failed to start]
```

What we do in Mock is just `podman start` and `podman exec`, without
--privileged option as non-root user.

Can the seccomp rules be updated to fix DNS resolution newer images?

This also affects Docker on RHEL 7 too.

> What we do in Mock is just `podman start` and `podman exec`, without
> --privileged option as non-root user.

I checked once more, and we are running it as the root user (bad).  Nevertheless,
I tested that both root/non-root scenario manually and it behaves the same.

Paul, can  you take a look at this please?

I think it also requires an update in libseccomp which is unlikely to happen in 7.9.

We have a definitive fix for this issue in RHEL 8 but it touches few components and it won't be backported to RHEL 7.

Could you just disable seccomp for F35 containers with `--security-opt seccomp=unconfined`?

@praiskup please see https://bugzilla.redhat.com/show_bug.cgi?id=2034209#c7

I think we could turn off seccomp for all images, not only F35?
https://github.com/rpm-software-management/mock/pulls

I mean: https://github.com/rpm-software-management/mock/pull/872

better not disable seccomp by default, just do that on RHEL7 when using Fedora35+ images with an updated glibc.

On RHEL 8 there is no need to disable seccomp because ENOSYS will be returned for syscalls unknown to the seccomp profile.

There will be no back ported fixes for RHEL7.  It no longer gets updated.  Disable seccomp or update to RHEL 8 is the only option.