Hi!
This is not an issue, just a question to help me understand what's going on.
Can see in sas.sh that it's required to manually mount the appimage payload prior to launching the contained executable via bwrap? Curious as to why is that the case -- is it not possible to give bwrap enough permissions so the appimage container may be ran directly using it, skipping the manual mount & unmount steps?
Additinally, first squashfuse is attempted for the mounting, and if it fails, dwarfs is given a go. Presumably because those two are the main imaging methods and mutually inoperable?
Hi!
This is not an issue, just a question to help me understand what's going on.
Can see in sas.sh that it's required to manually mount the appimage payload prior to launching the contained executable via
bwrap? Curious as to why is that the case -- is it not possible to give bwrap enough permissions so the appimage container may be ran directly using it, skipping the manual mount & unmount steps?Additinally, first
squashfuseis attempted for the mounting, and if it fails,dwarfsis given a go. Presumably because those two are the main imaging methods and mutually inoperable?