You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building an AppImage using a build of linuxdeploy from source. All seems to go well, no errors when running linuxdeploy, and the resulting .AppImage file is definitely non-empty (about 100MB size which makes sense given all the libraries that linuxdeploy pulls into the AppDir). Yet, when I run it I get execv error: No such file or directory, and if I run it instead with program.AppImage --appimage-mount and look in the folder at the mount point, it is completely empty.
Any ideas? It works fine on the same system if I use the linuxdeploy AppImage, but not when I use the version built from source. What am I missing?
The text was updated successfully, but these errors were encountered:
kpeeters
changed the title
AppImage built successfully yet mount shows it is empty?
AppImage built successfully yet --appimage-mount shows it is empty?
Aug 21, 2024
@kpeeters I just worked with a friend who had the same problem with one of my AppImages. I built it using the linuxdeploy container, building linuxdeploy from source (not that building it from source was related, just a commonality).
I am building an AppImage using a build of linuxdeploy from source. All seems to go well, no errors when running linuxdeploy, and the resulting .AppImage file is definitely non-empty (about 100MB size which makes sense given all the libraries that linuxdeploy pulls into the AppDir). Yet, when I run it I get
execv error: No such file or directory
, and if I run it instead withprogram.AppImage --appimage-mount
and look in the folder at the mount point, it is completely empty.Any ideas? It works fine on the same system if I use the linuxdeploy AppImage, but not when I use the version built from source. What am I missing?
The text was updated successfully, but these errors were encountered: