Hvad er APPIMAGE-filformatet?
En .appimage-fil er en komplet Linux-applikation pakket i én eksekverbar fil. Den samler programmet sammen med de delte biblioteker, det har brug for, så det kører på de fleste distributioner uden installation, en pakkehåndtering eller root-adgang. Formatet blev skabt af Simon Peter, blev først leveret i 2004 som *klik* og tog navnet AppImage i 2013. Det nuværende type 2-format, introduceret i 2016, er en ELF-eksekverbar fil med et komprimeret SquashFS-aftryk tilføjet efter den. Når du kører filen, monterer en lille runtime-stub dette aftryk med FUSE og starter AppRun-indgangspunktet indeni, så intet kopieres til dine systemmapper. Et ældre type 1-format brugte et .iso 9660-aftryk i stedet for SquashFS og er nu forældet. AppImage findes sammen med .flatpak og Snap som en distributionsuafhængig måde at levere Linux-software på, og det er udgivet under MIT-licensen.
Sikkerhed og tryghed
RISIKO: MEDIUMAn AppImage is an executable program, so running one is like running any downloaded native binary: it runs with your user privileges and can access your files. The format has no sandbox of its own and no mandatory signing, so only run AppImages from sources you trust and prefer downloads over HTTPS from the project's official site. Optional GPG signatures and update info exist but are not enforced.
Formatdetaljer
kort fortalt- Generic 'application image' output - Some imaging or rendering tools have used .appimage informally for an application-specific image dump, unrelated to the Linux AppImage bundle format.
Programmer der åbner APPIMAGE-filer
Tekniske detaljer
dyb specifikation| Encoding | Binary |
| Byte order | Little-endian (follows the host ELF and SquashFS layout) |
| Container | ELF executable with an appended filesystem image (type 2: SquashFS; type 1: ISO 9660 with Rock Ridge extensions) |
| Compression | SquashFS payload, commonly compressed with gzip, xz/LZMA, or zstd (type 2). Type 1 uses ISO 9660 with optional zisofs compression. |
| Encryption | None built into the format |
| Typical size | A few megabytes to several hundred megabytes, depending on bundled libraries and assets |
| Structure | A small ELF runtime stub at the start of the file mounts the appended filesystem image with FUSE at launch, then executes the AppRun entry point at the root of the mounted AppDir. The root also contains exactly one .desktop file, an application icon, and the bundled binaries, libraries, and resources. |
| Integrity | Optional embedded update information (zsync, gh-releases-zsync, or Pling transport) plus an optional embedded signature; SquashFS itself carries per-block metadata but no format-level hash of the whole file |
| Platforms | Linux |
| Structure Notes | Two format generations: type 1 (ISO 9660, now deprecated) and type 2 (SquashFS, current). Both are valid ELF executables that self-mount. Recent type 2 files support runtime flags such as --appimage-extract, --appimage-mount, and --appimage-offset. |
| Entry Point | AppRun (ELF binary or interpreted script) at the AppDir root |
| Runtime | Bundled runtime stub relies on FUSE (libfuse) on the host to mount the image without extraction; --appimage-extract works without FUSE |
| Udgivet | 2004 (as klik); renamed AppImage in 2013; type 2 format in 2016 |
| Seneste version | Type 2 |
| Åben standard | Ja · royaltyfri |
| Specifikation | github.com |
APPIMAGE-konverteringer
Fællesskabets Q&A
spurgt af brugereIngen spørgsmål endnu - vær den første til at spørge om APPIMAGE-filer.