Unbound issue on EL10

[StackKorora]

Greetings,
Testing team is in the process of adding all of the documentation guides into Sparky for validation testing (still very early stages at this time). While running tests against the Rocky 10 RC the unbound test failed. Upon investigation it seems that changes in 10 require a chroot while SELinux is enabled. It's a simple line addition that ( in my very quick and limited testing ) did not impact other Rocky versions. Thus, I recommend adding this change.

I am not an unbound expert. I'd love feedback on this change. Is it the best option? 🤷‍♂️ Is there a better option? 🤷‍♂️ I just found a solution that worked. 😁 We might even need to add a bit of documentation as to why we are adding this change. All of this is why I would like thoughts/feedback.

For my reference: https://access.redhat.com/articles/6980379

[sspencerwire]

@wale @StackKorora For these changes, I'm recommending that we make the change to the english .md file and remove the translation files. The English file will show up in Crowdin and at that time the change will be picked up by our translators. In the past, making these sort of changes on the translated files themselves caused Crowdin to become confused.

UPDATE... I've reverted the changes to the translated files and approved the change to the English file. Thanks @StackKorora

[github-actions]

Test results for 3463ba8:

Number of broken URLs: 7

URL,RESULT,FILENAME
 https://mattermost.com/,failed,guides/contribute/README.md
 https://ftp.gnu.org/gnu/tar/,failed,guides/backup/tar.md
 http://$(hostname):8080,failed,guides/repositories/pulp_fetch_upload.md
 https://mattermost.com,failed,desktop/tools/businessapps.md
 https://ftp.gnu.org/gnu/hello/hello-2.12.tar.gz,failed,labs/systems_administration_I/lab7-software_management.md
 https://www.stigviewer.com/stig/web_server/,failed,books/disa_stig/disa_stig_part3.md
 https://www.stigviewer.com/stig/red_hat_enterprise_linux_8/,failed,books/disa_stig/disa_stig_part1.md

[wale]

Hey @sspencerwire, you have got the wrong person again. [1] [2] You're looking for @wsoyinka.