[bug] [linuxdeploy] Linux AppImage script fails [podman] ['std::logic_error']

[leet4tari]

Describe the bug

Looking to offer a local build option for our tauri app for our Linux users, we ran into a number of user related issues like package versions mis-matching issues, none of these problems with the tauri-app, just a reason why I was looking at doing a docker build.

Tried to make this build process easier by documenting and testing how to use docker as a clean starting point, I ran into problems, because I had switched to using podman for my container loads.

Doing an AppImage build I got to the following failed bundle position, which I was not able to find any info on or for

    Bundling [tauri_bundler::bundle::linux::appimage] Tari Universe (Alpha)_1.6.1_amd64.AppImage (/work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha)_1.6.1_amd64.AppImage)
     Running [tauri_bundler::utils] Command `/root/.cache/tauri/linuxdeploy-x86_64.AppImage  --appimage-extract-and-run --verbosity 1 --appdir /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir --plugin gtk --plugin gstreamer --output appimage`
linuxdeploy version 1-alpha (git commit ID 659c9db), GitHub actions build 10 built on 2024-07-26 15:40:22 UTC
terminate called after throwing an instance of 'std::logic_error'
  what():  subprocess failed (exit code 127)
       Error [tauri_cli] failed to bundle project:
    - `failed to run /root/.cache/tauri/linuxdeploy-x86_64.AppImage`

As the basic build and the rpm/deb bundles were completing without any noticeable issues, I did not think I had anything wrong with our process. Plus I was able to build using GitHub action tauri-apps/tauri-action in our workflow.

Seems that FUSE storage options with podman need a little more effort, as podman is a little stricter. Some info can be found reading the ReadHat Blog - https://www.redhat.com/en/blog/podman-inside-container, thou you would not find the above error 'std::logic_error'

Running a container to build tauri-app in

podman run -it --rm  \
  --cap-add=sys_admin --cap-add mknod --device=/dev/fuse \
  -v ${PWD}/../temp/root:/root \
  -v ${PWD}/../universe:/work \
  -w /work \
  -u root \
  --platform linux/amd64 \
  ubuntu:22.04 bash

with --cap-add=sys_admin --cap-add mknod --device=/dev/fuse been the part needed to fix the above error.

This does not include all the package install and setups. This was for x86_64 host and guest container.

Reproduction

No response

Expected behavior

No response

Full tauri info output

root@f7e7c7bfc16c:/work# npm run tauri info

> tari-universe@1.6.1 tauri
> node ./scripts/tauri-wrapper.js info

Loading environment file: ./src-tauri/env.esme
[dotenv@17.2.2] injecting env (8) from src-tauri/env.esme -- tip: 📡 auto-backup env with Radar: https://dotenvx.com/radar

[✔] Environment
    - OS: Ubuntu 22.4.0 x86_64 (X64) (Unknown DE on Unknown Session)
    ✔ webkit2gtk-4.1: 2.48.5
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.90.0 (1159e78c4 2025-09-14)
    ✔ cargo: 1.90.0 (840b83a10 2025-07-30)
    ✔ rustup: 1.28.2 (e4f3ad6f8 2025-04-28)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 22.19.0
    - npm: 10.9.3

[-] Packages
    - tauri 🦀: 2.8.5
    - tauri-build 🦀: 2.4.1
    - wry 🦀: 0.53.3
    - tao 🦀: 0.34.3
    - tauri-cli 🦀: 2.8.4
    - @tauri-apps/api : 2.8.0
    - @tauri-apps/cli : 2.8.4

[-] Plugins
    - tauri-plugin-process 🦀: 2.3.0
    - @tauri-apps/plugin-process : not installed!
    - tauri-plugin-fs 🦀: 2.4.2
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-shell 🦀: 2.3.1
    - @tauri-apps/plugin-shell : 2.3.1
    - tauri-plugin-single-instance 🦀: 2.3.4
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-updater 🦀: 2.9.0
    - @tauri-apps/plugin-updater : not installed!
    - tauri-plugin-http 🦀: 2.5.2
    - @tauri-apps/plugin-http : not installed!
    - tauri-plugin-clipboard-manager 🦀: 2.3.0
    - @tauri-apps/plugin-clipboard-manager : 2.3.0
    - tauri-plugin-os 🦀: 2.3.1
    - @tauri-apps/plugin-os : 2.3.1
    - tauri-plugin-cli 🦀: 2.4.0
    - @tauri-apps/plugin-cli : not installed!

[-] App
    - build-type: bundle
    - CSP: style-src 'self' 'unsafe-inline'; object-src 'self' data: blob:; img-src 'self' data: blob: base64: https://*.twimg.com https://cdn.npmjs.com/@tari-project/tari-tower http://127.0.0.1 http://127.0.0.1/ http://127.0.0.1:* http://localhost http://localhost/ http://localhost:* https://static.tari.com https://static.tari.com/* https://lh3.googleusercontent.com; worker-src 'self' blob: https://cdn.npmjs.com/@tari-project/tari-tower; default-src 'self' tauri: https: http://localhost:* http://127.0.0.1:*; script-src-elem 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self' https: wss://ut.tari.com wss://relay.walletconnect.org https://rpc.ankr.com/eth https://ethereum-sepolia-rpc.publicnode.com tauri: tauri://localhost:* http://localhost:* http://127.0.0.1:* ipc: http://ipc.localhost data: blob: application/octet-stream base64; script-src 'self' 'unsafe-eval'; media-src 'self' data: blob: tauri: https:
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace

Additional context

No response

[FabianLars]

This was also discussed a bit on discord (though no mention of podman) here https://discord.com/channels/616186924390023171/1383929416798965932 (don't bother joining just for that, there wasn't much info - just crosslinking it here).

Since this error is not saying anything, a general workaround at the moment is to run cargo install tauri-cli --git https://github.com/tauri-apps/tauri --branch temp/linuxdeploy --force --locked until i revert the change that seemingly causes this error (most of the times, not sure about yours tbh) #13913

[leet4tari]

Thanks @FabianLars ... I did not see the libfuse commit. I was more opening the issue for direction on where I could possible put a PR in for a note or trouble shooting guide or at least have it found in the issues.

I will test on Monday, just for my own sanity and to really be thorough. I wonder if testing for fuse support might be an option? I don't even know how one might do that, but a suggestion.

Thanks for all the awesome tooling!

[FabianLars]

I was more opening the issue for direction on where I could possible put a PR in for a note or trouble shooting guide or at least have it found in the issues.

I'm unsure how to proceed with this whole issue either tbh. btw, thanks for figuring out what caused your issure 👍

I wonder if testing for fuse support might be an option? I don't even know how one might do that, but a suggestion.

No idea either but falling back to the old behavior doesn't sound reasonable so we may as well document the requirements (if we stick with what we currently have, which i kinda doubt) upfront and call it a day.

[leet4tari]

Doing the same AppImage bundle for linux-arm64 on a MacBook with an M1, but have a different error

ERROR: Failed to copy file /usr/share/doc/libxrender1/copyright to /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libxrender1/copyright: filesystem error: cannot copy file: Permission denied [/usr/share/doc/libxrender1/copyright] [/work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libxrender1/copyright]
Copying file /usr/share/doc/libxslt1.1/copyright to /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libxslt1.1/copyright
ERROR: Failed to copy file /usr/share/doc/libxslt1.1/copyright to /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libxslt1.1/copyright: filesystem error: cannot copy file: Permission denied [/usr/share/doc/libxslt1.1/copyright] [/work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libxslt1.1/copyright]
Copying file /usr/share/doc/libzstd1/copyright to /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libzstd1/copyright
ERROR: Failed to copy file /usr/share/doc/libzstd1/copyright to /work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libzstd1/copyright: filesystem error: cannot copy file: Permission denied [/usr/share/doc/libzstd1/copyright] [/work/src-tauri/target/release/bundle/appimage/Tari Universe (Alpha).AppDir/usr/share/doc/libzstd1/copyright]
failed to bundle project: `failed to run /root/.cache/tauri/linuxdeploy-aarch64.AppImage`
       Error [tauri_cli_node] failed to bundle project: `failed to run /root/.cache/tauri/linuxdeploy-aarch64

I don't know if it's related, but will be part of my testing on Monday. Again, this works in GitHub action, which is not podman, but the basic process does work.

[leet4tari]

I'm unsure how to proceed with this whole issue either tbh. btw, thanks for figuring out what caused your issure 👍

You welcome.

I wonder if testing for fuse support might be an option? I don't even know how one might do that, but a suggestion.

No idea either but falling back to the old behavior doesn't sound reasonable so we may as well document the requirements (if we stick with what we currently have, which i kinda doubt) upfront and call it a day.

Spit-balling, but having both ways and selection via an env or switch could work. But been able to detect if fuse does not work, use the old way that does not libfuse would be cool, but as I said, not sure if that is detectable. Selectable override might just be the way for the crazy podman people.

[brenoprata10]

Any updates to share about this topic? I am also facing the same issue hahaha

[FabianLars]

Try this please

cargo install tauri-cli --git https://github.com/tauri-apps/tauri --branch fix/linuxdeploy-extractrun
cargo tauri build

Edit: branch was merged just now, new command would be

cargo install tauri-cli --git https://github.com/tauri-apps/tauri
cargo tauri build

but i think the next release will be relatively soon.