Sad to hear about the flood damage! Hope everything is ok! I’ll set a docker compose and add it to the documentation as the “official” setup.
I’m not sure about your environment (are you running Debian?), bu maybe you can try:
Possible Solutions
./drafft-appimagefile --no-sandboxim using on my home system Tuxedo os with dual boot arch (arch is mainly used for me for experimenting with the kernel).thats based on ubuntu but runs kde environment. on my work system im using rhel.
the no sandbox doesnt always work, i tried that solution that refused to open the software, no errors just sat with a blank terminal line. has done that in a few other flatpaks, such as affine. and the set uid option i tested as well that gave me a segfault crash, no idea why, So far the only way i was able to get it running was to extract it. and set the sandbox to root. and add 4577 to it. it ran perfect after that.
that leads me to begin to question appimages in their current state. (as a whole not your product as it happening on a lot of other app images as well.) the problem with it is most people are not like myself, if it isnt a simple fix, they will simply move on to an alternative, they wont debug or try and solve it. thats one of the reasons i mention it here. i love the drafft software and want it to succeed.