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
Simply add `NO_STRIP=true` before your build command:
21
+
Pake CLI now automatically retries AppImage builds with `NO_STRIP=1` when linuxdeploy fails to strip the binary. To skip the strip step from the very first attempt (or when scripting your own builds), set the variable manually:
This bypasses the library stripping process that often causes issues on certain Linux distributions.
@@ -50,7 +50,7 @@ sudo apt install -y \
50
50
pkg-config
51
51
```
52
52
53
-
Then try building again with `NO_STRIP=true`.
53
+
Then try building again (you can still pre-set `NO_STRIP=1` if you prefer).
54
54
55
55
**Solution 3: Use DEB Format Instead**
56
56
@@ -60,16 +60,21 @@ DEB packages are more stable on Debian-based systems:
60
60
pake https://example.com --name MyApp --targets deb
61
61
```
62
62
63
-
**Solution 4: Use Docker**
63
+
**Solution 4: Use Docker (with FUSE access)**
64
64
65
-
Build in a clean environment without installing dependencies:
65
+
Build in a clean environment without installing dependencies. AppImage tooling needs access to `/dev/fuse`, so run the container in privileged mode (or grant FUSE explicitly):
0 commit comments