probonopd edited this page May 12, 2018 · 25 revisions

AppImages require FUSE to run. Filesystem in Userspace (FUSE) is a system that lets non-root users mount filesystems.

Install FUSE

Many distributions have a working FUSE setup out-of-the-box. However if it is not working for you, you may need to install and configure FUSE manually.

For example, on Ubuntu:

sudo apt-get install fuse
sudo modprobe fuse
sudo groupadd fuse

sudo usermod -a -G fuse $user

For example, on openSUSE:

sudo zypper install fuse

In order to use fusermount on OpenSUSE with the default (?) "secure" file permission settings (see /etc/, your login needs to be part of the trusted group. To add yourself, run

sudo usermod -a -G trusted `whoami`

Then log out and log in for the change to take effect.

For example, on CentOS/RHEL:

yum --enablerepo=epel -y install fuse-sshfs # install from EPEL
usermod -a -G fuse "$user" 

For example, on Armbian 64-bit systems (e.g., for the Pine64) you need to install 32-bit libfuse2 in order to run 32-bit AppImages such as the MuseScore one:

sudo apt install libfuse2:armhf

Chrome OS, Chromium OS

FUSE does not seem to be operational out of the box; check for updates


If you don't want to install FUSE, you can either mount or extract the AppImage.

type-2 AppImage

To extract the contents of the AppImage, simply run the AppImage with --appimage-extract.

type-1 AppImage

If the above does not work, you may still have an older type-1 AppImage. To mount the AppImage and run the application, simply run

sudo mount -o loop Some.AppImage /mnt

A type-1 AppImage is an ISO, so

sudo apt install libarchive-tools # Or any other method to get `bsdtar`
mkdir AppDir
cd AppDir
bsdtar xfp /home/me/Downloads/Some.AppImage

also works.


When running an AppImage from a Docker container you will get the following error:

fuse: failed to open /dev/fuse: Operation not permitted
Could not mount AppImage
Please see

You'll often hear "oh, just add these arguments to docker run --cap-add SYS_ADMIN --cap-add MKNOD --device /dev/fuse:mrw and it'll work", but that is totally insecure and not recommended, as it bypasses security restrictions which have been implemented for very good reasons.

Instead, just extract the AppImage in your build script:

./appimagetool-*.AppImage --appimage-extract
# AppImage contents have been extracted to a directory called squashfs-root, which might be changed in the 
squashfs-root/AppRun <any argument that you'd normally pass directly to appimagetool-*.AppImage>
# clean up a bit
rm -rf squashfs-root/

Note: appimagetool-*.AppImage can be extracted starting with release version 9

If you want to decide whether to use the AppImage directly or extracted depending on whether you're in a container or not, for example in a build script, you can combine this with some detection code.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.