Hi all. I’ve successfully installed Bisq on TAILS, but I ran into a few minor issues along the way.
I want to update the wiki. There’s a link to log in, but no way to register. Am I able to get permission to update the wiki? Or can someone make the changes for me?
The command service onion-grater restart must be replaced with systemctl restart onion-grater.service
The command “mv ~/.local/share/Bisq/* /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq” will fail. This can be fixed by running these two commands first:
sudo mkdir -p /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq
sudo chown amnesia:amnesia /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq
The use of “dotfiles” in TAILS can be confusing for newbies. It would be helpful to include a link to the TAILS documentation:
Tails - Persistent Storage
The Bisq wiki says that user data only needs to be moved to the dotfiles after running it for the first time. However, if Bisq ever creates any NEW files, they will be lost on reboot unless they are also copied to the dotfiles.
(The persistent dotfiles directory in TAILS only creates links for files, not directories. Newly created files are not automatically made persistent just because they are part of Bisq’s directory structure.)
- User installs Bisq in Tails according to the wiki.
- User runs Bisq, waits for it to sync, exits, and copies user data to dotfiles.
- User reboots, runs Bisq and creates a wallet password.
- Bisq creates new wallet files in non-persistent home directory.
- User reboots, and finds that Bisq has lost all wallet data.
For that reason, I think it’s necessary to move user data to the dotfiles before rebooting EVERY time that Bisq has been used. This can be done by running the above mv command again. It will cause errors for files/links that already exist, which can be safely ignored:
mv /home/amnesia/.local/share/Bisq/* /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq
Hope that helps someone.