sudo not available to owner of system from the AppImage FUSE Filesystem.

[offternet]

1. I want to execute a bash command from AppImage that requires the sudo password without having to hack out of AppImage FUSE Filesystem.

2. I have accomplished this by breaking from a termial parent process I launched in a AppImage by executing a new gnome-terimal --window and using yad script below to enter sudo password and execute sudo apt-get update:

#!/bin/bash
function update () {
if yad --form --field="Password":H --separator="" | sudo -S true; then
sudo apt-get update || yad --text="Update failed"
sudo -k && echo "." && echo "Next Command...."
else
yad --text="Wrong password"
fi
}
export -f update

yad --width=400 --height=500 --button="Update":"bash -c update" --button="Exit:1".

3. Issue: trying to just execute the sudo apt-get update command from within the AppImage FUSE Filesystem:

"error output "sudo: /usr/local/bin/sudo must be owned by uid 0 and have the setuid bit set`"

4. It appears AppImage has been configure to block all sudo access from the FUSE filesystem it hides under directory /tmp/*....

[probonopd]

Hi @offternet. As written in AppImage/appimagetool#92 (comment):

how this is possible, "sudo apt-get udpate" from a bash script within the AppImage".

You need to run your AppImage with sudo ./Your.AppImage and your application inside the AppImage needs to run apt-get udpate (no sudo).

[probonopd]

export PATH="${HERE}/usr/bin" has to be export PATH="${HERE}/usr/bin:$PATH" of course.

[TheAssassin]

@probonopd's comment provides the most likely fix: what you do right now removes the system's $PATH. You should not overwrite but prepend your own value.

Also, I'm not sure it's wise to add your AppDir to $PATH. You do not have to do so to run a single binary. Binaries like sudo are available on your base system anyway and would be picked up anyway. The same goes for binaries like apt-get. Your bundling might even be incomplete (you can test that by starting a VM of, e.g., Fedora, Ubuntu, Linux Mint, and trying to run your AppImage there).

The goal of your AppImage still remains unclear to me.

[probonopd]

Looks like he wants to make some Gtk frontend that runs apt commands.

[TheAssassin]

But then there's no point in bundling apt. Perhaps this is a huge misconception and it all originates from overwriting $PATH completely in the AppRun script?

[offternet]

@TheAssassin @probonopd I tested same AppImage without modifications on a different Debian build and this time it worked to run apt-get update WITHOUT apt-get being within the AppImage. I appoligize for taking up your time on this situtation.
I did not append the AppImage path with :$PATH

On Both Debian builds the system $PATH ENV are exactly the same: /usr/bin:/usr/local/bin:/usr/local/games:/usr/games. What is different between the to Debian Builds are: The failing build is Sparkylinux 7.6 Debian Trixie and the version that works is Debian 12 bookworm.

Will try over next few days to isolate what the conflict is on the previous Debian Build, Sparkylinux7.6

@probonopd you are correct. I am using Yad GUI gtk frontend but, was NOT using yad code during apt-get update test.

Again, sorry for wasting your time.

[offternet]

I know what I am doing is not the conventional (not recommended) method for executing parent shell script from within an AppImage FUSE filesystem that then executes a child gnome-termial sub process. However, I was able to immediately find the solutions for the next 2 issues related to my method; Had it not been for our previous conversations I would still be searching / bother others and maybe for sometime. Thank You Again !

---

Error 1: gnome-termial (same as curl command) = "File not found"
Solution: -- Set $PATH ENV in the Parent Shell script which is executed in the FUSE filesystem.

#!/bin/bash
PATH="/bin:/usr/bin:/usr/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gnome-terminal"

---

Error 2: Unable to create proxy for gnome-terminal child process "dbus-launch"
Solution: -- sudo apt install dbus-x11

sudo no longer required on the AppImage file.

• setting the PATH in parent now allows me to run script in FUSE filesystem mount as user and NOT root.
• Putting the Parent script in root would not work with yad gui function calls.
• I can now use sudo command for each gnome-terminal child process as needed.

I will soon share my findings and a video (in corret topic area) of more advance use of yad GUI that is contained in and executed from an AppImage.

AGAIN !! THANK YOU !!!!