AppImage - Revision history

Prabuanand: removed the external website

2026-01-25T13:12:24Z

removed the external website

← Older revision		Revision as of 13:12, 25 January 2026
Line 30:		Line 30:
	== See also ==		== See also ==

	* [https://xplshn.github.io/AppBundleHUB/ - AppImages that run on Musl]]

	[[Category:Software]]		[[Category:Software]]

Prabuanand: added warning, link to external site with appimages built for musl

2026-01-25T13:07:59Z

added warning, link to external site with appimages built for musl

← Older revision		Revision as of 13:07, 25 January 2026
Line 1:		Line 1:
	{{Draft\|work in progress}}		{{Draft\|work in progress}}

	[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that AppImages require glibc, and Alpine Linux uses [[musl]].		[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that many AppImages require glibc, and Alpine Linux uses [[musl]].

	== Installation ==		== Installation ==

	First you need {{Pkg\|fuse}} for AppImages to work; then, modprobe it.		First you need {{Pkg\|fuse}} for AppImages to work; then, modprobe it.
	{{Cmd\|# apk add fuse		{{Cmd\|# apk add fuse

	<nowiki>#</nowiki> modprobe fuse}}		<nowiki>#</nowiki> modprobe fuse}}
	Optional, but recommended: install ~~[https://git.adelielinux.org/adelie/gcompat~~ gcompat] for [[Running_glibc_programs\|glibc compatibility]].		Optional, but recommended: install {{pkg\|gcompat}} package for [[Software_management#Running_glibc_programs\|glibc compatibility]].
	{{Cmd\|# apk add gcompat}}		{{Cmd\|# apk add gcompat}}

	Download your AppImage to the user's directory~~: launching it as root is typically a '''security risk''' and unnecessary~~. The {{Path\|~/.local/bin}} location is suitable, further to [https://specifications.freedesktop.org/basedir/latest/#variables XDG Base Directory Specifications]. {{Path\|~/bin}} is another common location. Create the directory, if necessary. It is good practice to ensure that the location for your AppImages appears in the user's {{Path\|$PATH}} for executables so that the AppImages could be launched from a shell (aka 'terminal') without needing to specify their path. To check, from a user's prompt:		== Download AppImage ==
	{{Cmd\|$ echo $PATH}}
			Download your AppImage to the user's directory. The {{Path\|~/.local/bin}} location is suitable, further to [https://specifications.freedesktop.org/basedir/latest/#variables XDG Base Directory Specifications]. {{Path\|~/bin}} is another common location. {{Warning\|Downloading or launching AppImages as root is a '''security risk''' and should be avoided.}}

			Create the above mentioned directory, if necessary. It is good practice to ensure that the location for your AppImages appears in the user's {{Path\|$PATH}} for executables so that the AppImages could be launched from a shell (aka 'terminal') without needing to specify their path. To check, from a user's prompt: {{Cmd\|$ echo $PATH}}

	For AppImages to appear in an app launcher, additionally, a {{Path\|.desktop}} file with the AppImage's name would need to be created or found upstream and used if licence permits, placing it in {{Path\|~/.local/share/applications}}.		For AppImages to appear in an app launcher, additionally, a {{Path\|.desktop}} file with the AppImage's name would need to be created or found upstream and used if licence permits, placing it in {{Path\|~/.local/share/applications}}.

	You have to make the AppImage executable so that you can launch it.		== Usage ==
	{{Cmd\|$ chmod +x <var>Example</var>.AppImage}}
			You have to make the downloaded AppImage executable so that you can launch it: {{Cmd\|$ chmod +x <var>Example</var>.AppImage}}

			To execute it, for example, when the current working directory of your user prompt is the directory where the AppImage is stored, then you can instruct your shell that the AppImage to be launched is located in that same directory by using the prefix {{ic\|./}}:{{Cmd\|$ ./<var>Example</var>.AppImage}}

			If the AppImage was stored in the user's {{Path\|$PATH}} for executables, neither navigating to the shell to use the {{ic\|./}} prefix nor stating the path as a prefix would be necessary to execute it:{{Cmd\|$ <var>Example</var>.AppImage}}

	== ~~Usage~~ ==		== See also ==
	To execute it, for example, when the current working directory of your user prompt is the directory where the AppImage is stored, then you can instruct your shell that the AppImage to be launched is located in that same directory by using the prefix {{ic\|./}}:
	~~{{Cmd\|$ ./<var>Example</var>.AppImage}}~~

	~~If the AppImage was stored in the user's {{Path\|$PATH}} for executables, neither navigating to the shell to use the {{ic\|~~./~~}} prefix nor stating the path as a prefix would be necessary to execute it:~~		* [https://xplshn.github.io/AppBundleHUB/ - AppImages that run on Musl]]
	~~{{Cmd\|$ <var>Example<~~/~~var>.AppImage}}~~

	[[Category:Software]]		[[Category:Software]]

Samedev at 15:58, 20 January 2026

2026-01-20T15:58:00Z

← Older revision		Revision as of 15:58, 20 January 2026
Line 1:		Line 1:
			{{Draft\|work in progress}}

	[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that AppImages require glibc, and Alpine Linux uses [[musl]].		[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that AppImages require glibc, and Alpine Linux uses [[musl]].

John3-16: 1. Added internal links to 'Running glibc programs' and to 'fuse' package; 2. Added paragraph re storage location; root being discouraged; $PATH; and .desktop; 3. Moved chmod to 'Installation'; 4. Removed 'Example' subheading to demonstrate two usage models depending on paths; 5. Added Category: Software; 6. Style and grammar amendments, using Cmd template, and 'var' for variables.

2025-11-14T05:26:01Z

1. Added internal links to 'Running glibc programs' and to 'fuse' package; 2. Added paragraph re storage location; root being discouraged; $PATH; and .desktop; 3. Moved chmod to 'Installation'; 4. Removed 'Example' subheading to demonstrate two usage models depending on paths; 5. Added Category: Software; 6. Style and grammar amendments, using Cmd template, and 'var' for variables.

← Older revision		Revision as of 05:26, 14 November 2025
Line 1:		Line 1:
	[https://appimage.org AppImages] allow a simple executable like experience ~~on Linux~~, but the problem is that AppImages require glibc and ~~alpine~~ uses [[musl]].		[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that AppImages require glibc, and Alpine Linux uses [[musl]].

	== Installation ==		== Installation ==
	First you need ~~FUSE~~ for AppImages to work ~~and~~ modprobe it.		First you need {{Pkg\|fuse}} for AppImages to work; then, modprobe it.
	~~<pre>~~		{{Cmd\|# apk add fuse
	# apk add fuse
	# ~~modprobe fuse~~		<nowiki>#</nowiki> modprobe fuse}}
	</~~pre~~>		Optional, but recommended: install [https://git.adelielinux.org/adelie/gcompat gcompat] for [[Running_glibc_programs\|glibc compatibility]].
	Optional but recommended install [https://git.adelielinux.org/adelie/gcompat gcompat] for glibc compatibility.		{{Cmd\|# apk add gcompat}}
	~~<pre>~~
	# apk add gcompat		Download your AppImage to the user's directory: launching it as root is typically a '''security risk''' and unnecessary. The {{Path\|~/.local/bin}} location is suitable, further to [https://specifications.freedesktop.org/basedir/latest/#variables XDG Base Directory Specifications]. {{Path\|~/bin}} is another common location. Create the directory, if necessary. It is good practice to ensure that the location for your AppImages appears in the user's {{Path\|$PATH}} for executables so that the AppImages could be launched from a shell (aka 'terminal') without needing to specify their path. To check, from a user's prompt:
	</~~pre~~>		{{Cmd\|$ echo $PATH}}

			For AppImages to appear in an app launcher, additionally, a {{Path\|.desktop}} file with the AppImage's name would need to be created or found upstream and used if licence permits, placing it in {{Path\|~/.local/share/applications}}.

			You have to make the AppImage executable so that you can launch it.
			{{Cmd\|$ chmod +x <var>Example</var>.AppImage}}

	== Usage ==		== Usage ==
	~~You have to make~~ the AppImage ~~executable~~, so you can ~~execute it~~.		To execute it, for example, when the current working directory of your user prompt is the directory where the AppImage is stored, then you can instruct your shell that the AppImage to be launched is located in that same directory by using the prefix {{ic\|./}}:
	~~===~~ Example ~~===~~		{{Cmd\|$ ./<var>Example</var>.AppImage}}
	<~~pre~~>
	~~$ chmod +x Example~~.AppImage		If the AppImage was stored in the user's {{Path\|$PATH}} for executables, neither navigating to the shell to use the {{ic\|./}} prefix nor stating the path as a prefix would be necessary to execute it:
	$ ./Example.AppImage		{{Cmd\|$ <var>Example</var>.AppImage}}
	~~</pre>~~
			[[Category:Software]]

Samedev at 19:24, 11 November 2025

2025-11-11T19:24:51Z

← Older revision		Revision as of 19:24, 11 November 2025
Line 7:		Line 7:
	# modprobe fuse		# modprobe fuse
	</pre>		</pre>
	Optional but recommended install gcompat for glibc compatibility.		Optional but recommended install [https://git.adelielinux.org/adelie/gcompat gcompat] for glibc compatibility.
	<pre>		<pre>
	# apk add gcompat		# apk add gcompat

Samedev: A bit of editing. Just needed to get gud at wikitext.

2025-11-11T19:22:20Z

A bit of editing. Just needed to get gud at wikitext.

← Older revision		Revision as of 19:22, 11 November 2025
Line 1:		Line 1:
	AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl.		[https://appimage.org AppImages] allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses [[musl]].

			== Installation ==
			First you need FUSE for AppImages to work and modprobe it.
			<pre>
			# apk add fuse
			# modprobe fuse
			</pre>
			Optional but recommended install gcompat for glibc compatibility.
			<pre>
			# apk add gcompat
			</pre>

			== Usage ==
			You have to make the AppImage executable, so you can execute it.
			=== Example ===
			<pre>
			$ chmod +x Example.AppImage
			$ ./Example.AppImage
			</pre>

Samedev: Created page with "AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl."

2025-11-11T19:11:28Z

Created page with "AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl."

New page

AppImages allow a simple executable like experience on Linux, but the problem is that AppImages require glibc and alpine uses musl.

← Older revision		Revision as of 13:07, 25 January 2026
Line 1:		Line 1:
	{{Draft\|work in progress}}		{{Draft\|work in progress}}

	[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that AppImages require glibc, and Alpine Linux uses [[musl]].		[https://appimage.org AppImages] allow a simple executable-like experience, but the problem is that many AppImages require glibc, and Alpine Linux uses [[musl]].

	== Installation ==		== Installation ==

	First you need {{Pkg\|fuse}} for AppImages to work; then, modprobe it.		First you need {{Pkg\|fuse}} for AppImages to work; then, modprobe it.
	{{Cmd\|# apk add fuse		{{Cmd\|# apk add fuse

	<nowiki>#</nowiki> modprobe fuse}}		<nowiki>#</nowiki> modprobe fuse}}
	Optional, but recommended: install ~~[https://git.adelielinux.org/adelie/gcompat~~ gcompat] for [[Running_glibc_programs\|glibc compatibility]].		Optional, but recommended: install {{pkg\|gcompat}} package for [[Software_management#Running_glibc_programs\|glibc compatibility]].
	{{Cmd\|# apk add gcompat}}		{{Cmd\|# apk add gcompat}}

	Download your AppImage to the user's directory~~: launching it as root is typically a '''security risk''' and unnecessary~~. The {{Path\|~/.local/bin}} location is suitable, further to [https://specifications.freedesktop.org/basedir/latest/#variables XDG Base Directory Specifications]. {{Path\|~/bin}} is another common location. Create the directory, if necessary. It is good practice to ensure that the location for your AppImages appears in the user's {{Path\|$PATH}} for executables so that the AppImages could be launched from a shell (aka 'terminal') without needing to specify their path. To check, from a user's prompt:		== Download AppImage ==
	{{Cmd\|$ echo $PATH}}
			Download your AppImage to the user's directory. The {{Path\|~/.local/bin}} location is suitable, further to [https://specifications.freedesktop.org/basedir/latest/#variables XDG Base Directory Specifications]. {{Path\|~/bin}} is another common location. {{Warning\|Downloading or launching AppImages as root is a '''security risk''' and should be avoided.}}

			Create the above mentioned directory, if necessary. It is good practice to ensure that the location for your AppImages appears in the user's {{Path\|$PATH}} for executables so that the AppImages could be launched from a shell (aka 'terminal') without needing to specify their path. To check, from a user's prompt: {{Cmd\|$ echo $PATH}}

	For AppImages to appear in an app launcher, additionally, a {{Path\|.desktop}} file with the AppImage's name would need to be created or found upstream and used if licence permits, placing it in {{Path\|~/.local/share/applications}}.		For AppImages to appear in an app launcher, additionally, a {{Path\|.desktop}} file with the AppImage's name would need to be created or found upstream and used if licence permits, placing it in {{Path\|~/.local/share/applications}}.

	You have to make the AppImage executable so that you can launch it.		== Usage ==
	{{Cmd\|$ chmod +x <var>Example</var>.AppImage}}
			You have to make the downloaded AppImage executable so that you can launch it: {{Cmd\|$ chmod +x <var>Example</var>.AppImage}}

			To execute it, for example, when the current working directory of your user prompt is the directory where the AppImage is stored, then you can instruct your shell that the AppImage to be launched is located in that same directory by using the prefix {{ic\|./}}:{{Cmd\|$ ./<var>Example</var>.AppImage}}

			If the AppImage was stored in the user's {{Path\|$PATH}} for executables, neither navigating to the shell to use the {{ic\|./}} prefix nor stating the path as a prefix would be necessary to execute it:{{Cmd\|$ <var>Example</var>.AppImage}}

	== ~~Usage~~ ==		== See also ==
	To execute it, for example, when the current working directory of your user prompt is the directory where the AppImage is stored, then you can instruct your shell that the AppImage to be launched is located in that same directory by using the prefix {{ic\|./}}:
	~~{{Cmd\|$ ./<var>Example</var>.AppImage}}~~

	~~If the AppImage was stored in the user's {{Path\|$PATH}} for executables, neither navigating to the shell to use the {{ic\|~~./~~}} prefix nor stating the path as a prefix would be necessary to execute it:~~		* [https://xplshn.github.io/AppBundleHUB/ - AppImages that run on Musl]]
	~~{{Cmd\|$ <var>Example<~~/~~var>.AppImage}}~~

	[[Category:Software]]		[[Category:Software]]