@girish This still seems to be an issue. I tried it last night to see if I could reproduce it and sure enough I could. I think this is a bug, unless I'm doing something wrong?
Here's the steps I took (if you want to reproduce it):
Create new server
Connected via SSH and ran the following commands:
sudo apt-get update
sudo fdisk /dev/sdb
sudo mkfs.ext4 /dev/sdb1
sudo mkdir /mnt/cloudron-boxdata
sudo mount /dev/sdb1 /mnt/cloudron-boxdata
sudo nano /etc/fstab
sudo wget https://cloudron.io/cloudron-setup
sudo chmod +x ./cloudron-setup
sudo ./cloudron-setup
(reboot)
sudo systemctl stop box
sudo systemctl stop docker
DATA_DIR="/mnt/cloudron-boxdata"
sudo mkdir -p "${DATA_DIR}"
sudo mv /home/yellowtent/boxdata "${DATA_DIR}"
sudo ln -s "${DATA_DIR}/boxdata" /home/yellowtent/boxdata
sudo systemctl start docker
sudo systemctl start box
(reboot, though tried without rebooting here too)
Restore Cloudron from backup (in my case located on OVH Object Storage if that part matters at all). It will fail at this part, after a minute or two it will give the error from the screenshot
in the comments above around "
/home/yellowtent/boxdata is not a valid path"
Can someone please confirm if my steps are invalid or if there's truly a bug here?
