Closed samcday closed 8 months ago
Figured it out. Running cargo tauri build
during Docker build doesn't work. Removing that step from Dockerfile.build
and then instead running docker run --rm -it image cargo tauri build
works fine.
I'm very curious as to why this is, but I burned half a day on this problem. I'm not feeling adventurous enough to go exploring. I guess Docker build environment has some serious shenanigans going on behind the scenes.
If anyone should ever stumble on this and figures it out, I'd love to know! :)
Describe the bug
I can't seem to produce a valid AppImage build from inside a Docker container. I've tried with legacy Docker, BuildKit Docker, and I've tried using
ubuntu:focal
,rust:1-bookworm
,rust:1-buster
Docker Hub images. In every case, the produced image segfaults immediately on startup.My host system is a fully up to date Arch install, and I've also confirmed the same behaviour on my Steam Deck (which is also an Arch derivative).
Reproduction
Expected behavior
An AppImage produced from a
ubuntu:focal
container can be run on other Linux systems.Full
tauri info
outputStack trace
No response
Additional context
No response