For the complete documentation index, see llms.txt. This page is also available as Markdown.

FUSE

Required by some formats for mounting the image

Most self-contained formats mount their own payload rather than unpacking it, and FUSE is what lets a normal user mount something. Whether you need anything installed for that depends on the runtime the package was built with.

Traditional AppImages, built with linuxdeploy or similar, are the ones that need FUSE on the host, usually the older libfuse2 that many distributions no longer install by default.

Common errors

fusermount: mount failed: Operation not permitted
Cannot mount AppImage, please check your FUSE setup
dlopen(): error loading libfuse.so.2

Solutions

Extract instead

The fix that needs nothing installed. Most AppImages support it:

./app.AppImage --appimage-extract-and-run
APPIMAGE_EXTRACT_AND_RUN=1 ./app.AppImage

Or unpack it once and run what comes out:

./app.AppImage --appimage-extract
./squashfs-root/AppRun

Install FUSE

Debian/Ubuntu:

Fedora:

Arch:

Use a package that does not need it

A static runtime that carries its own mounting code and falls back on its own is the real fix. That is what Anylinux AppImages do, and it is why the packages in soarpkgs rarely run into any of this.

Last updated