[qubes-users] snap issues, related to the filesystem outside of ~/ ?

I tried installing snaps in a debian template and then 

but while it ran fine the first time, after restarting it stopped working. As I wanted to be sure it was not a qubes issue I [posted on the snapcraft forum](https://forum.snapcraft.io/t/authy-snap-error-cannot-perform-operation-mount-rbind/24932) and the question they asked that made me think it was qubes related was

   *"Is this being run inside a container? It seems to imply that either /dev or /tmp/snap.rootfs_IeI049/ do not exist, but previously in the log the tmp dir was created by snap-confine"*

So, AFAIK i installed it according to the [qubes instructions](https://www.qubes-os.org/doc/software-update-domu/#installing-snap-packages) but am getting various errors that are starting to point to the ephemeral nature of appvms (only the home dir is retained).

Anyone know how to fix this?

Snaps now litter across the file system, so are no longer the
user-specific install they seemed to be.
I don't think there is a simple fix - you cant use bind-dirs for the
devices under /dev, and I'm guessing the /tmp directory is created per
boot.

Thanks unman, its a pity, i very much prefer just using a repo, or perhaps a flatpak but there are some apps (authy in this case) that i cant seem to install any other way... maybe wine but not sure its worth the hassle?