The signal desktop app does something to identify the host that it is running on. When moving to another host, all one’s messages are no longer available (unless someone can correct me). Being stuck on a specific host is a pain.
Has anyone been successful at migrating from a host to an LXD container for running the signal desktop app? So far I have tried:
keeping the same host name
keeping the same mac addr
exposing the home, username, uid, gid so that it is the same as before
using container rather than VM
It is not clear to me what identifying info signal is using.
The signal desktop app does something to identify the host that it is running on. When moving to another host, all one’s messages are no
longer available (unless someone can correct me). Being stuck on a specific host is a pain.
Has anyone been successful at migrating from a host to a container for running the signal desktop app? So far I have tried:
1 keeping the same host name
2 keeping the same mac addr
3 exposing the home, username, uid, gid so that it is the same as before
4 using container rather than VM
It is not clear to me what identifying info signal is using.
Any help/pointers would be greatly appreciated.
Thanks.
Visit Topic or reply to this email to respond.
To unsubscribe from these emails, click here.
Could you give an example on what the signal desktop app is?
This runs on mobile devices and desktops (linux, windows, mac). I want to run it in an lxd container rather than on the metal. But doing so means I lose previous communications.