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.

Hi

 From seeing the bug, it seems that we don't support unbound with chroot.
    
    Bug 1113947 - Add unbound-chroot systemd service for running unbound in the chroot (edit)
    https://bugzilla.redhat.com/show_bug.cgi?id=1113947

On the other hand,we are talking about chroot command here.

Is there nothing with unbound chroot , or anything wrong with the description?

In short,I was wondering whether unbound is supported with chroot or not.

Thank you very much in advance.

Reported by: rhn-support-shgao

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.5_release_notes/new_features_networking#annotations:d81534d4-0f1c-4bb3-86bb-f43e1ea71caf

We definitely do not recommend running unbound under chroot. SELinux system protection in enforcing mode provides much better security. If SELinux is enforcing then protection is already strong enough and chroot does not improve it significantly. Protection by chroot is lower and I would recommend to consider it only when SELinux cannot be kept in enforcing mode.

I think we may prepare support article with steps required to have working unbound in chroot environment. But unlike bind we have not prepared special package with helpers, because it should not be necessary.

Thanks a lot for the input!

The new release note is now published:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.9_release_notes/new_features#BZ-2121623

linking to the new article: https://access.redhat.com/articles/6980379