 | |
| Filename extension |
.AppImage
|
|---|---|
| Magic number | 41 49 02 (3 bytes hexadecimal from offset 8) |
| Developed by | Simon Peter |
| Initial release | 2004; 20 years ago (2004) |
| Latest release |
13 |
| Container for | Software installation |
| Open format? | Yes |
| Free format? | Yes |
| Website | appimage |
AppImage (formerly known as klik and PortableLinuxApps) is an open-source format for distributing portable softwareonLinux. It aims to allow the installation of binary software independently of specific Linux distributions, a concept often referred to as upstream packaging. As a result, one AppImage can be installed and run across Ubuntu, Arch Linux, and Red Hat Enterprise Linux without needing to use different files. It aims to be a format that is self-contained, rootless, and independent of the underlying Linux distribution.[1]
Released first in 2004 under the name klik, it was continuously developed, then renamed in 2011 to PortableLinuxApps and later in 2013 to AppImage. Version 2 was released in 2016.
AppImage's predecessor, klik, was designed in 2004 by Simon Peter.[2] The client-side software is licensed under the GNU GPL. klik integrated with web browsers on the user's computer. Users downloaded and installed software by typing a URL beginning with klik://. This downloaded a klik "recipe" file, which was used to generate a .cmg file. For the main ingredients, pre-built .deb packages from Debian Stable repositories were usually fed into the recipe's generation process. This way, one recipe could be used to supply packages to a wide variety of platforms. With klik, only eight programs could be run at once because of the limitation of mounting compressed images with the Linux kernel, unless FUSE was used. The file was remounted each time the program was run, meaning the user could remove the program entirely by simply deleting the file. The next version, klik2, was in development and would natively incorporate the FUSE kernel module, but it never reached past the beta stage.[3] Around 2011, the klik project went dormant, and the website went offline.[4]
Simon Peter started a successor project named PortableLinuxApps with similar goals around that time.[5] The technology was adopted, for instance, by the "portablelinuxgames.org" repository, which provided hundreds of mostly open-source video games.[6]
Around 2013, the software was renamed again from portableLinuxApps to AppImage; the license became the MIT license. AppImage is the format, and AppImageKit is a concrete open-source implementation. The development happens in a GitHub repository.[7]
In 2016, Version 2 of the AppImage specification was drafted. Version 2 is unrestricted in filesystem type (a draft implementation used SquashFS).[8][9] It removes the fixed offset for where the filesystem image begins in the file and enabled digital signatures to be embedded directly in the AppImage as opposed to as a separate file.
AppImage aims to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, portability, distro agnosticism, no installation, no root permission, and keeping the underlying operating system untouched.[10] Because of this, AppImage does not install software by placing executables in various locations. Instead, the file is a single filesystem image itself. When run, the file is mounted with FUSE. AppImage is designed to be simpler to use than traditional installer formats such as Deb and RPM, since it is not necessary to modify the operating system or user environment.
Each file is self-contained; it includes all libraries the application depends on that are not already part of the targeted system. A version 1.0 AppImage is an ISO 9660 Rock Ridge file (which can be optionally compressed via zisofs) containing a minimal AppDir and a runtime.[11]
AppImage allows the embedding of digital signatures, which need to be verified externally. The format does not require signatures to be validated, only that they may be included.[12] AppImage does not enforce sandboxing, but it may be done by some applications.[13]
In 2007, Klik was the inspiration for Alexander Larsson's glick project, the precursor of Flatpak.[14]
In 2015, Linus Torvalds, creator of the Linux kernel, said that "[t]his is just very cool. I finally got around to play with the "AppImage" version of Subsurface, and it really does seem to "just work"."[15] Mark Shuttleworth stated that "AppImages are a pretty clean experience and I admire the work behind them."[16]
|
| |
|---|---|
| dpkg |
|
| RPM |
|
| Embedded systems |
|
| Distribution-agnostic |
|
| Others (binary) |
|
| Others (source) |
|
| Front-ends |
|
| Related topics |
|
| |
