ci: Disable apparmor user namespace restrictions in GH Guix action

[UdjinM6]

Issue being fixed or feature implemented

actions/runner-images#10015

What was done?

actions/runner-images#10443 (comment)

How Has This Been Tested?

develop: https://github.com/UdjinM6/dash/actions/runs/13187780750
this PR: https://github.com/UdjinM6/dash/actions/runs/13187795136

Breaking Changes

n/a

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

[PastaPastaPasta]

I was wondering what broke guix a little while ago on GitHub ci! Good find :)

[coderabbitai]

Walkthrough

The pull request introduces a new step in the build job within the GitHub Actions workflow. Before the repository is checked out, the workflow now runs a command that disables AppArmor restrictions on unprivileged user namespaces by modifying the kernel parameter. This addition ensures that subsequent Docker operations can proceed without interference from AppArmor. The overall structure of the workflow, including code checkout, dependency caching, the Guix build process, and artifact handling, remains intact. No changes have been made to the declarations of any exported or public entities.

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96dd126 and df34f0e.

📒 Files selected for processing (1)

• .github/workflows/guix-build.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: Build (linux64_ubsan, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_tsan, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_sqlite, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_nowallet, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_fuzz, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64_cxx20, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (linux64, x86_64-pc-linux-gnu, linux64)
• GitHub Check: Build (arm-linux, arm-linux-gnueabihf, arm-linux)

🔇 Additional comments (1)

.github/workflows/guix-build.yml (1)

75-78: Disable AppArmor Restrictions Step – Key CI Configuration
The newly added step disables AppArmor user namespace restrictions via sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0, ensuring that subsequent Docker operations under the Guix build environment run without interference. This command is appropriately placed before the main checkout and build steps.

As a best practice, consider adding an inline comment with a reference to the relevant GitHub issues (e.g., actions/runner-images#10015) for future maintainers and traceability.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[knst]

utACK

It looks similar to issue that I had on my kubuntu

[PastaPastaPasta]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

utACK df34f0e
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQCuOfQAhZ8i0Ua8F/i89eRbnItOAUCZ6ZetQAKCRDi89eRbnIt
OLEuAQDvbu7cQjLTM+jR2eR9sND/9qyW/OJG2JyY7uelMaecMAD/SUoUmnHesvty
MqQIoeoqJHIRTbweRkUPsdavC2K1dws=
=/Fdg
-----END PGP SIGNATURE-----