Conversation
AppImageKit's runtime dlopens libfuse.so.2, which Ubuntu 22.04+ and Fedora no longer install by default, so the nightly AppImage failed to start there. uruntime uses FUSE when available and otherwise falls back to mount namespaces or extract-and-run. Pinned to v0.7.1. Refs #136 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WrqyVv7K7HAEYqiG5pyauK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses the FUSE part of #136.
The AppImage is built with AppImageKit's
continuousruntime, which requires libfuse2. Ubuntu 22.04+ and Fedora don't install it by default, so the nightly AppImage fails at startup with:This swaps the
--runtime-filepassed to appimagetool for uruntime'suruntime-appimage-squashfs-${arch}(the runtime Anylinux AppImages use). It uses FUSE when it can, otherwise falls back to mount namespaces or extract-and-run. It's a drop-in: same appimagetool invocation, same squashfs AppDir, both x86_64 and aarch64 assets exist. It's also pinned to a tag (v0.7.1) instead of the movingcontinuousrelease.Tested
Built
stimulator-x86_64.AppImagewith the script on Ubuntu 24.04 with no libfuse2 installed:error loading libfuse.so.2.--appimage-versionreportsv0.7.1, the runtime starts the bundled deno and the app runs until it looks uplibadwaita-1.so.0, which the test container doesn't have (GTK4/libadwaita are expected from the host, as before).deno fmt --check/deno lintpass. aarch64 was not built locally, but theuruntime-appimage-squashfs-aarch64asset exists at the pinned tag.Not in scope
This does not make the AppImage run on Alpine/musl. The runtime itself is static musl, but the bundled
denois glibc and GTK4/libadwaita still come from the host. Full Anylinux support would mean bundling glibc + the GTK4 stack with sharun. Since@sigmasd/gtkloads GTK via FFIdlopen, those libs would have to be listed by hand, so that's a separate, larger change.🤖 Generated with Claude Code
https://claude.ai/code/session_01WrqyVv7K7HAEYqiG5pyauK
Generated by Claude Code