-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mock in Docker container fails: "Insufficient rights." (with --privileged/--cap-add=SYS_ADMIN permissions) #1487
Comments
Using the "fedora:39" container works fine, i.e. the issue is related to Fedora 40. The version of Mock in Fedora 39 is the same:
|
This is the end of the strace output of the Mock run on Fedora 40. It may help to locate the problem:
|
Thank you for the report. But I can not reproduce this with Is this a failure of consolehelper? Can you check if it is an SUID binary?
|
I have the same issue – worked a few days before.
|
I may have found an answer: this was a new cluster/node and it had AppArmor enabled. Disabling it on the node and rebooting it cleared the problem. I am not very well-oriented in AppArmor, but I wonder if there's a less radical solution (tuning vs turning it off). Either way, doesn't seem to be a |
Short description of the problem
Running "mock -h" inside a "fedora:40" or "fedora:latest" Docker container (with --privileged/--cap-add=SYS_ADMIN) since a few days just prints "Insufficient rights.", without any further useful information. Mock worked before, also in GitHub Actions. There is probably a recent change, or a recent configuration update of Fedora, breaking Mock in containers.
Output of
rpm -q mock
mock-5.9-1.fc40.noarch
Steps to reproduce issue
The output is always: "Insufficient rights."
Any additional notes
Output of
mock --debug-config
:Insufficient rights.
The text was updated successfully, but these errors were encountered: