I'm attaching a persistent disk to my VM that uses a deep learning image (the one I've been using is common-cu113-v20221017-ubuntu-2004), but the disk (which shows up under /dev/sdb is automatically being mounted at the mount point /home/jupyter. How can I keep this from happening?
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 55.6M 1 loop /snap/core18/2566
loop1 7:1 0 63.2M 1 loop /snap/core20/1623
loop2 7:2 0 299M 1 loop /snap/google-cloud-cli/75
loop4 7:4 0 67.8M 1 loop /snap/lxd/22753
loop5 7:5 0 49.6M 1 loop /snap/snapd/17883
loop6 7:6 0 55.6M 1 loop /snap/core18/2632
loop7 7:7 0 63.2M 1 loop /snap/core20/1695
loop8 7:8 0 91.8M 1 loop /snap/lxd/23991
sda 8:0 0 50G 0 disk
├─sda1 8:1 0 49.9G 0 part /
├─sda14 8:14 0 4M 0 part
└─sda15 8:15 0 106M 0 part /boot/efi
sdb 8:16 0 100G 0 disk /home/jupyter
It looks like /home/jupyter is pre-populated in the deep learning VM:
$ ls /home/jupyter/
snap/ src/ tutorials/
The problem I'm facing is that there are files on the persistent disk, which I was hoping to mount at /mnt/disks/workspace-disk, but if I follow the main persistent disk attachment guide, then all that shows up at /mnt/disks/workspace-disk are the files that existed under /home/jupyter.
Thanks for the help :)
