-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
troubleshooting: warn about secure boot #4614
Conversation
Hi @bfallik. Thanks for your PR. I'm waiting for a containers member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @mrunalp |
@bfallik You need to sign your PR |
@rhatdan ah, thanks. The lack of signature is probably because I created the PR directly from the Github UI. |
@rhatdan updated, i think |
Changes LGTM if we can figure out the gating issue. |
troubleshooting.md
Outdated
@@ -429,3 +428,17 @@ You'll need to either: | |||
or as root if your user has not enough privileges. | |||
|
|||
* sudo loginctl enable-linger $UID | |||
|
|||
### 18) `podman run` fails with "bpf create: permission denied error" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is an extra space at the end of this line that is causing the tests to fail. Remove the space and repush and we should be able to merge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch @rhatdan
Add an additional troubleshooting item to warn users that Secure Boot can prevent Podman from running containers. The error messages and initial debugging steps don't make it clear that this all stems from a BIOS setting. Hopefully adding this item to the troubleshooting doc will avoid future headaches. Signed-off-by: Brian Fallik <[email protected]>
I pushed a new commit without the whitespace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bfallik, giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM thanks @bfallik ! |
/lgtm |
Add an additional troubleshooting item to warn users that Secure Boot can prevent Podman from running containers. The error messages and initial debugging steps don't make it clear that this stems from a BIOS setting. Hopefully adding this item to the troubleshooting doc will avoid future headaches.