Skip to content

Sorting out yet another AppImage breakage. #1947

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

Merged
merged 1 commit into from
Jul 26, 2025

Conversation

nicolasnoble
Copy link
Member

Copy link
Contributor

coderabbitai bot commented Jul 25, 2025

Walkthrough

The Linux CI workflow was updated to allow container access to /dev/fuse with additional security options. The Dockerfile now installs libfuse2t64, updates the appimagetool download URL, and uses a prebuilt AppImage for appimage-builder instead of pip installation and patching. The custom patch handling package version comparison was removed.

Changes

File(s) Change Summary
.github/workflows/linux-build.yml Added --device /dev/fuse, --cap-add SYS_ADMIN, and --security-opt apparmor:unconfined to container options.
tools/build/Dockerfile Installed libfuse2t64 and fuse, updated appimagetool URL, switched to prebuilt appimage-builder AppImage, removed pip install and patch steps.
tools/build/appimage-dpkg.patch Deleted patch file removing Package class with version comparison logic from appimage-builder.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

In the warren where builds hop and run,
A FUSE device now joins the fun!
AppImages leap with a shiny new tool,
Old patches retire, the Docker stays cool.
With every tweak, the CI grows bright—
Rabbits rejoice in the Linux build night!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 24629ca and e5244ae.

📒 Files selected for processing (3)
  • .github/workflows/linux-build.yml (1 hunks)
  • tools/build/Dockerfile (1 hunks)
  • tools/build/appimage-dpkg.patch (0 hunks)
💤 Files with no reviewable changes (1)
  • tools/build/appimage-dpkg.patch
✅ Files skipped from review due to trivial changes (1)
  • .github/workflows/linux-build.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • tools/build/Dockerfile
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: pcsx-redux (x86_64-linux)
  • GitHub Check: pcsx-redux (aarch64-linux)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: asan
  • GitHub Check: coverage
  • GitHub Check: cross-arm64
  • GitHub Check: build-openbios
  • GitHub Check: macos-build-and-test-toolchain
  • GitHub Check: toolchain
  • GitHub Check: build
  • GitHub Check: aur-build
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @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.

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (1)
tools/build/Dockerfile (1)

51-53: Collapse the three RUN layers, pin version & add checksum for appimage-builder.

Multiple layers slow the build and, again, an unchecked binary is fetched.

-RUN wget -O appimage-builder-x86_64.AppImage https://github.com/AppImageCrafters/appimage-builder/releases/download/v1.1.0/appimage-builder-1.1.0-x86_64.AppImage
-RUN chmod +x appimage-builder-x86_64.AppImage
-RUN mv appimage-builder-x86_64.AppImage /usr/local/bin/appimage-builder
+RUN curl -L -o /usr/local/bin/appimage-builder \
+     https://github.com/AppImageCrafters/appimage-builder/releases/download/v1.1.0/appimage-builder-1.1.0-x86_64.AppImage && \
+    echo "SHASUM  /usr/local/bin/appimage-builder" | sha256sum -c - && \
+    chmod +x /usr/local/bin/appimage-builder

Again, replace SHASUM with the official checksum.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8f8cc3d and 24629ca.

📒 Files selected for processing (3)
  • .github/workflows/linux-build.yml (1 hunks)
  • tools/build/Dockerfile (1 hunks)
  • tools/build/appimage-dpkg.patch (0 hunks)
💤 Files with no reviewable changes (1)
  • tools/build/appimage-dpkg.patch
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (11)
  • GitHub Check: pcsx-redux (x86_64-linux)
  • GitHub Check: pcsx-redux (aarch64-linux)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: build
  • GitHub Check: macos-build-and-test-toolchain
  • GitHub Check: aur-build
  • GitHub Check: asan
  • GitHub Check: cross-arm64
  • GitHub Check: build-openbios
  • GitHub Check: coverage
  • GitHub Check: toolchain

Comment on lines 40 to 43
# AppImage dependencies
RUN apt install -y libfuse2t64

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Consider adding fuse & required capabilities, not only the userspace library.

libfuse2t64 provides the userspace library, but AppImages still need the FUSE kernel module and the fusermount helper.
On Ubuntu 24.04 those come from the fuse package. In addition, mounting inside the container requires the SYS_ADMIN capability (or --privileged) in the runtime options. Only adding /dev/fuse will still lead to EPERM at mount-time.

Tagging so this does not regress CI again.

🤖 Prompt for AI Agents
In tools/build/Dockerfile around lines 40 to 42, the Dockerfile installs only
the userspace library libfuse2t64, but it also needs the fuse package to provide
the FUSE kernel module and fusermount helper. Update the Dockerfile to install
the fuse package alongside libfuse2t64. Additionally, ensure that the container
runtime is configured with the SYS_ADMIN capability or run with --privileged to
allow mounting, as adding /dev/fuse alone will cause permission errors.

Comment on lines +44 to 50
RUN wget https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage && \
chmod +x /tmp/appimagetool-x86_64.AppImage && \
cd /opt && /tmp/appimagetool-x86_64.AppImage --appimage-extract && \
mv squashfs-root appimage-tool.AppDir && \
ln -s /opt/appimage-tool.AppDir/AppRun /usr/bin/appimagetool && \
rm /tmp/appimagetool-x86_64.AppImage
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Pin the download & verify checksum of appimagetool for supply-chain safety.

The build now pulls appimagetool from the continuous channel each time.
That URL always points to the latest artefact, so the resulting image is no longer reproducible and the hash is not verified.

-RUN wget https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage && \
+RUN curl -L -o appimagetool-x86_64.AppImage \
+     https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage && \
+     echo "SHASUM  appimagetool-x86_64.AppImage" | sha256sum -c - && \

Replace SHASUM with the published hash (or a pinned tag instead of continuous).

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In tools/build/Dockerfile around lines 44 to 49, the appimagetool is downloaded
from the continuous channel without pinning to a specific version or verifying
its checksum, which compromises build reproducibility and supply-chain security.
To fix this, replace the URL to download a specific tagged release version of
appimagetool instead of continuous, and add a step to verify the downloaded
file's checksum against the published hash before proceeding with extraction and
installation.

@nicolasnoble nicolasnoble merged commit b2066c7 into grumpycoders:main Jul 26, 2025
27 of 29 checks passed
@nicolasnoble nicolasnoble deleted the appimage-bullshit branch July 26, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant